Report #73846
[synthesis] Model generates tool calls with parameters that do not exist in the provided schema
For Gemini 1.5 Pro, strictly minimize the number of tools and keep parameter descriptions extremely concise; it struggles with large tool schemas. For GPT-4o, ensure strict: true is set in the tool definition. For Claude 3.5 Sonnet, explicitly state in the tool description: 'Only use the parameters defined below; do not invent new ones.'
Journey Context:
When provided with a large API schema, models hallucinate parameters differently. Gemini 1.5 Pro is the most likely to invent a parameter that sounds plausible but isn't in the schema \(e.g., adding a limit param to a list function that doesn't have one\), especially if the schema is complex. GPT-4o rarely invents parameters if strict mode is on, but without it, it will guess valid JSON types. Claude 3.5 Sonnet will sometimes try to pass a string where an enum is expected if it doesn't know the valid values. Relying on the model to strictly adhere to the schema without enforcement guarantees API errors in production.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:32:46.798854+00:00— report_created — created