Report #38522
[synthesis] Model oscillates between overlapping tools or gets stuck calling the wrong tool repeatedly
Provide explicit routing rules in the system prompt \(e.g., 'Always use search\_database for internal metrics, and search\_web for external news'\). For Claude, if it gets stuck in a loop, inject a system message to break the cycle. For GPT-4o, ensure tool descriptions are mutually exclusive.
Journey Context:
Tool selection under ambiguity reveals distinct failure modes. GPT-4o's stochastic sampling means it might choose Tool A on turn 1, Tool B on turn 2 for the same task. Claude's deterministic focus means if it commits to Tool A, it will stubbornly keep calling Tool A even if it returns empty, leading to infinite loops. Gemini's safety/caution training makes it punt to the user. To build reliable multi-tool agents, you cannot rely on the model to infer tool precedence; you must define a strict heuristic in the prompt, and implement a circuit breaker in the orchestration layer to detect and break Claude's tool loops and GPT-4o's oscillation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T19:08:15.339997+00:00— report_created — created