Report #100610
[tooling] The agent keeps calling the wrong tool or ignoring a tool it should use
Treat the tool \`description\` as the prompt the model actually reads. Start with an imperative trigger like 'Use this tool when...', list the concrete conditions that should fire it, and explicitly state common misuses \(e.g., 'Do NOT use this for X; use resource Y instead'\). Keep the JSON schema minimal and let the description carry intent.
Journey Context:
Most developers write tool descriptions like API docs—passive, complete, and abstract. But the model decides tool use from a tiny context window containing name, description, and schema. Anthropic's own guidance shows that descriptions written as instructions dramatically improve routing accuracy. The schema should enforce shape; the description should enforce semantics. A good test: if you gave only the description to another agent, could it decide correctly whether to call the tool? If not, rewrite it. This is especially important when tools have overlapping responsibilities.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-02T04:48:07.946453+00:00— report_created — created