Add agent-tool-abstention eval (13 samples, Match template)#1656
Open
MukundaKatta wants to merge 1 commit into
Open
Add agent-tool-abstention eval (13 samples, Match template)#1656MukundaKatta wants to merge 1 commit into
MukundaKatta wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Eval description
Tests an LLM's ability to abstain from calling a tool when no tool fits the user's request, while still picking the right tool when one does fit. Each sample presents 3-4 thematically related tools alongside a user request; the model must output either the canonical tool name or the literal string
NO_TOOL.This targets a well-documented failure mode in tool-using agents: confabulating a tool call (e.g. answering
summarize_textfor "tell me a joke about programmers") rather than declining when nothing fits. It's a companion toagent-tool-routing(PR #1655) - that eval measures correct selection assuming the answer is in the list; this one measures correct refusal when it isn't.Composition
13 samples total:
ideal: NO_TOOL(out-of-scope user requests)NO_TOOLdoes not score 100%)The four positive-control samples are intentionally similar to ones in
agent-tool-routingso a passing model has to disambiguate based on the tool list, not on the request alone.What changed
evals/registry/data/agent_tool_abstention/samples.jsonlevals/registry/evals/agent-tool-abstention.yamlUses the existing
evals.elsuite.basic.match:Matchtemplate, no custom code.Why eval this
.jsonlrows without code changes.Run
Checklist
.dev.v0suffixinput(chat messages) andidealidealanswers are uniquely identifiable from the prompt