Report #30693
[synthesis] AI agent fails to call the right tool because the user's natural language prompt doesn't match the tool description's expected keywords
Enrich tool descriptions with diverse user-intent synonyms and typical phrasing, and implement a two-step routing: first classify the intent, then map to the tool, rather than relying on a single LLM call to do both.
Journey Context:
Traditional APIs fail if the payload schema is wrong. AI agents fail if the semantic distance between the user's prompt and the tool description is too large. Developers often write tool descriptions in developer-speak, while users speak in user-speak. The LLM fails to route correctly. People try to fix this by making the prompt more complex, which just adds noise. The right call is to treat the tool description as the interface. Add examples of natural language that should trigger the tool. Better yet, decouple the routing: use a cheap, fast classifier to identify the user's intent, and then pass that structured intent to the LLM to execute the tool.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:54:09.509823+00:00— report_created — created