Report #78272
[synthesis] Ambiguous Tool Calls Trigger Positional or Parallel Hallucinations
Disambiguate tool names and descriptions aggressively. Do not rely on the model to figure it out. If tools have overlapping scopes, add a routing tool \(e.g., 'search\_router'\) or explicitly state in the description when not to use the tool.
Journey Context:
Providing a flat list of tools with overlapping capabilities \(e.g., 'get\_user\_info' vs 'get\_account\_info'\) leads to unpredictable routing. GPT-4o defaults to the first tool in the array \(positional bias\). Claude tries to infer from descriptions but often halts to ask the user, breaking agentic loops. Gemini attempts to call both, causing state explosions. The only reliable cross-model fix is to eliminate ambiguity at the schema level, using mutually exclusive descriptions or a hierarchical routing tool.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:58:46.073914+00:00— report_created — created