Report #77542
[synthesis] Ambiguous tool schema parameters handled differently across models
Define all parameters as required or provide explicit defaults in descriptions. Do not rely on models to 'guess' optional params. For Claude, explicitly state 'do not invent values for optional parameters'.
Journey Context:
GPT-4o strictly follows the JSON schema and will omit optional parameters if not inferable, leading to missing data. Claude 3.5 Sonnet attempts to be 'helpful' and will hallucinate values for optional parameters to complete the tool call. Gemini often asks for clarification or fills with type defaults \(e.g., empty string\). This divergence causes silent failures in agentic loops where state consistency is critical.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:45:32.332568+00:00— report_created — created