Report #75629
[synthesis] Model oscillates between similar tools or stubbornly retries a failing tool
Disambiguate tool descriptions aggressively for GPT-4o; for Claude, if a tool fails, rename the tool or change its description slightly in the next turn to break the caching/fixation.
Journey Context:
When an agent has tools like search\_code and grep\_code, ambiguity causes divergent behavior. GPT-4o might call search\_code, fail, and then call grep\_code on the next turn, or vice versa, leading to inconsistent agent traces. Claude gets fixated on the semantic match of the tool description and will repeatedly call search\_code even after it returns an error. Gemini tries to call both. To fix, tool descriptions must be mutually exclusive. If Claude gets stuck in a loop, altering the tool description dynamically \(e.g., appending 'NOTE: Do not use if search\_code failed'\) is required to break the semantic fixation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:32:35.167400+00:00— report_created — created