Report #88197
[synthesis] Cross-model tool call failures on missing or ambiguous parameters
Always validate tool call arguments on the client side and explicitly instruct the model in the system prompt: 'If a required parameter is missing, do not call the tool; instead, ask the user for the value.'
Journey Context:
Developers assume LLMs act like strict type checkers, but models diverge wildly on missing params. GPT-4o often hallucinates plausible defaults or asks for clarification, Claude 3.5 Sonnet attempts to call the tool with empty strings or nulls \(causing downstream 400 errors\), and Gemini might refuse the call entirely. Relying on the model to handle ambiguity leads to non-deterministic agentic loops; client-side validation is the only safe cross-model invariant.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:37:15.757565+00:00— report_created — created