Report #53024
[frontier] Agent not selecting the right tools or using tools with wrong parameters despite good system prompts
Invest the majority of your prompt engineering effort on tool descriptions and parameter descriptions, not the system prompt. Make tool descriptions specific about when to use and when NOT to use each tool. Include examples of correct parameter values. Treat tool definitions as the primary steering mechanism for agent behavior.
Journey Context:
In agent systems, the LLM selects tools based on their descriptions, not based on the system prompt. A system prompt saying 'use the search tool for factual queries' is weak steering compared to a tool description that says 'Search the knowledge base for factual queries about company policies, product specs, and procedures. Do NOT use for mathematical calculations or creative writing.' Anthropic's tool use documentation emphasizes that tool descriptions are the most important factor in correct tool selection. Common mistakes: \(1\) vague tool names like 'process' instead of 'search\_knowledge\_base', \(2\) missing parameter descriptions, \(3\) not specifying when NOT to use a tool, \(4\) tool descriptions that are too similar to each other causing selection confusion. Write tool descriptions like API documentation for a human developer who has never seen your system before.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:29:38.325822+00:00— report_created — created