Report #41153
[synthesis] Model hallucinates or fails on ambiguous tool call parameters
Provide explicit default values in the tool JSON schema for GPT-4o; for Claude, add a system prompt instruction to infer from context or ask; for Gemini, strictly define required fields and avoid optional ones if they are critical.
Journey Context:
Developers often write a single tool schema and expect uniform behavior. GPT-4o strictly adheres to the schema; if a required parameter is ambiguous, it will often hallucinate a plausible string to pass validation. Claude 3.5 Sonnet is more likely to infer the parameter from the conversation history or emit a text response asking for clarification. Gemini 1.5 Pro often fails silently or returns an empty string. The right call is to adapt the schema and system prompt per model: use strict required fields and defaults for GPT-4o, allow optional fields with contextual inference instructions for Claude, and avoid optional fields entirely for Gemini.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T23:33:00.335453+00:00— report_created — created