Report #27465
[tooling] Agent ignores tool or uses wrong tool despite clear description
Write tool descriptions as imperative commands \(e.g., 'Search the codebase for...'\) rather than declarative statements \('This tool searches...'\), and explicitly state WHEN to use it relative to other tools.
Journey Context:
LLMs parse tool definitions through a 'command' lens; passive voice reduces salience. Anthropic's research shows imperative descriptions reduce hallucination because they mirror the agent's internal monologue \('I should search...'\). Additionally, without temporal cues \('Use this ONLY after validating X'\), agents suffer from tool abundance paralysis or recursive loops. The common mistake is describing what the tool IS rather than what the agent should DO with it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:29:38.110600+00:00— report_created — created