Tool Avoidance
Agent answers from memory when current/source-grounded tool use is required.
10 patterns for this goal
Tool selection fails when agents avoid necessary tools and attempt tasks without them, select the wrong tool for the task, select unsafe tools, overuse a single tool for multiple different tasks, or don’t understand when different retrieval channels should be used. The 10 selection patterns documented here cover the challenge of choosing tools correctly — from misunderstanding tool capabilities through sequencing errors (using tools in wrong order) to unsafe or untrusted tool selection. Tool selection is upstream of invocation and reliability: selecting the wrong tool guarantees failure regardless of how correctly it’s invoked.
Tool-selection failures result from incomplete understanding of tool capabilities and context. Agents select wrong tools because they don’t understand what each tool does, when to use it, or what its limitations are. The mitigation is explicit tool discovery and capability documentation: maintain a registry of tools with clear descriptions of what each does, test agent tool selection by injecting tool-selection probes (does agent select the right tool for this task?), and add guardrails to prevent unsafe tool selections (require human approval before selecting dangerous tools).
Maintain clear, concise tool descriptions that describe the task each tool solves and when it should be used. Test agent tool selection with various tasks and verify the right tool is selected for each. Consider adding tool-selection validation (agent submits tool choice, human or automated validator approves before execution).
Depends on the task: if accuracy matters and a tool provides better accuracy, use the tool. If latency matters and skipping the tool is fast enough, consider skipping it. Make the tradeoff explicit in tool selection logic.
Document tool precedence (if Tools A and B both apply, prefer A in these cases, B in those cases). Use tool precedence to break ties consistently.
| Pattern | Mechanism |
|---|---|
| Tool Avoidance | Agent avoids available tool; attempts task without tool; results degrade |
| Tool Capability Misunderstanding | Agent misunderstands tool capabilities; selects tool for wrong task or thinks tool can’t do task it can |
| Tool Conflict Unresolved | Multiple tools apply; agent doesn’t resolve conflict; behavior undefined |
| Tool Overuse | Agent uses one tool for multiple different tasks; tool isn’t suitable for all uses |
| Tool Sequencing Error | Tools must be used in specific order; agent uses wrong order; fails or produces wrong results |
| Unsafe Tool Selection | Agent selects tool that is unsafe or should require approval in this context |
| Untrusted Tool Result Acceptance | Agent accepts tool result without validation; result is wrong or untrusted |
| Wrong Environment | Tool is appropriate for one environment (test) but not another (prod); agent selects for wrong environment |
| Wrong Retrieval Channel | Multiple ways to retrieve same data; agent selects wrong channel; retrieval fails or inefficient |
| Wrong Tool Selected | Agent selects wrong tool for task; tool is not appropriate for this task |
Total: 10 patterns
Agent answers from memory when current/source-grounded tool use is required.
Agent assumes a tool can do something it cannot.
Agent receives conflicting tool outputs and picks one without rationale.
Agent calls tools unnecessarily, increasing cost and latency.
Agent calls write tool before reading/verifying current state.
Agent uses destructive capability for exploratory work.
Agent treats malformed, stale, or injected tool output as authoritative.
Agent acts in production instead of staging, wrong tenant, or wrong project.
Agent searches public web instead of internal/private source or vice versa.
Agent chooses an inappropriate tool for the task.