Report #49410
[synthesis] Agent selects tools based on superficial keyword matches in descriptions, leading to misuse of tools whose actual implementation diverges from the description
Write tool descriptions that include Anti-patterns or Do NOT use this tool for X sections, and provide few-shot examples of correct vs. incorrect usage directly in the tool's docstring.
Journey Context:
Function calling matches descriptions to intent, but LLMs are lazy learners. The synthesis reveals that tool descriptions are essentially one-shot prompt engineering problems embedded inside the agent loop. If the description doesn't explicitly rule out anti-patterns, the agent will find them. Descriptions written for humans focus on what the tool does; LLMs need to know what the tool doesn't do, and how it fails. Adding negative constraints drastically reduces the search space and prevents catastrophic tool selection.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:25:14.031958+00:00— report_created — created