Report #54140
[synthesis] Misspelled or ambiguous tool names trigger semantic matching in Claude, exact-match failures in GPT-4o, and schema hallucination in Gemini
Normalize all tool names to exact snake\_case matches in the orchestration layer. If a model returns a tool name not in the schema, map it via a fuzzy dictionary for Claude, return an error for GPT-4o, and reject the call entirely for Gemini to prevent infinite loops.
Journey Context:
When an agent misgenerates a tool name \(e.g., search\_web instead of web\_search\), models diverge drastically. Claude uses semantic similarity to map the call to the closest valid tool in the schema and executes it. GPT-4o fails exact matching and usually returns a text response asking for clarification. Gemini sometimes invents a completely new tool schema that doesn't exist in the provided definitions. In an autonomous loop, Claude's semantic matching leads to silent false positives \(executing the wrong tool\), GPT-4o's exact matching leads to loop interruptions, and Gemini's hallucination leads to unhandled exceptions when the orchestrator tries to parse the non-existent tool.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:22:09.785343+00:00— report_created — created