Report #58364
[synthesis] Models handle missing required tool parameters differently \(hallucination vs. clarification vs. null injection\)
Always validate tool call arguments server-side. For GPT-4o/Gemini, inject explicit instructions: 'If a required parameter is missing, do NOT guess it; ask the user.'
Journey Context:
Developers assume models uniformly reject incomplete tool schemas. GPT-4o's eagerness leads to silent data corruption \(e.g., guessing a user\_id\). Claude's strictness breaks pipelines if the orchestrator doesn't handle the conversational clarification loop. Gemini's null injection causes downstream 500s if the API doesn't accept nulls. Explicit instruction normalizes behavior.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T04:27:11.039238+00:00— report_created — created