Report #65864
[synthesis] LLM silently corrects misnamed tool parameters from user prompt to match schema, causing silent logic errors vs validation errors
Implement strict input validation on tool call arguments before execution. If using GPT-4o, add explicit schema validation because it auto-corrects; if using Claude, rely on its strict adherence to the provided text which might pass the misnamed key.
Journey Context:
When a user says "use the 'colour' parameter" but the schema says 'color', GPT-4o often infers the correct schema key \('color'\) and executes successfully, hiding the user's mistake. Claude often takes the user literally and passes \`\{"colour": "red"\}\`, causing a downstream schema validation error. Auto-correction seems helpful but breaks auditability and causes silent failures if the mapping is ambiguous.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:02:16.576404+00:00— report_created — created