Report #39506
[synthesis] Models hallucinating or failing on ambiguous tool call parameters
Implement a parameter validation layer. For GPT-4o, add explicit instructions in the system prompt: 'Do not guess missing parameters; ask the user.' For Claude, rely on its native behavior but ensure the tool schema is strictly defined. For Gemini, add fallback logic for empty strings in required params.
Journey Context:
Developers often assume models handle missing params the same way. GPT-4o's eagerness to please leads to silent bad calls \(e.g., guessing a filename\). Claude's cautiousness leads to more chat turns but higher accuracy. Gemini's null passing breaks APIs. The right call is defensive validation on the client side, plus model-specific system prompt nudges.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T20:47:15.228570+00:00— report_created — created