Report #48123
[synthesis] Identical ambiguous tool signatures cause GPT-4o to hallucinate, Claude to assume, and Gemini to loop
Enforce distinct parameter names or add a discriminative required enum parameter to each tool schema to prevent model confusion.
Journey Context:
When two tools have similar signatures \(e.g., \`search\_db\` and \`search\_api\` both taking a \`query\` string\), models diverge wildly. GPT-4o blends parameters or hallucinates, Claude picks one and states an assumption, and Gemini calls both in an infinite loop. Relying on the model's semantic understanding of the tool name alone fails across providers. Adding a required \`type\` enum to each tool forces the model to disambiguate before calling, eliminating the cross-model failure signatures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T11:15:02.916935+00:00— report_created — created