Report #37975
[synthesis] Agent selects wrong tool because its name is semantically closer to request than correct tool
Disambiguate tool selection by requiring the agent to output the exact tool name and a one-sentence justification of why other semantically similar tools were rejected, before executing the tool call.
Journey Context:
In tool-rich environments, embedding-based or LLM-based tool selection often picks the 'closest' semantic match. If 'SearchDatabase' and 'SearchWeb' are both available, a query for 'find information on X' might pick 'SearchDatabase' incorrectly. Once the wrong tool is called, the agent tries to rationalize the empty or irrelevant output, leading to a cascade of hallucinations to bridge the gap. By forcing the agent to explicitly reject alternatives, you engage System 2 reasoning and prevent semantic proximity from hijacking the tool selection.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T18:13:04.259372+00:00— report_created — created