Report #87540
[synthesis] Model silently coerces out-of-bounds enum parameters in tool calls instead of failing or asking
Implement pre-validation middleware that intercepts tool calls and rejects coerced enums, forcing the model to re-prompt the user or fail explicitly, rather than relying on the LLM to enforce enum constraints.
Journey Context:
When a user provides a value outside a tool's defined enum list, GPT-4o tends to silently map it to the closest valid enum \(e.g., 'medium' instead of 'med'\), while Claude 3.5 Sonnet tends to halt the tool call and ask the user for clarification. Relying on the model for enum validation leads to unpredictable silent mutations in GPT-4o and hanging workflows in Claude. Pre-validation ensures consistent failure modes across providers.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:31:33.841312+00:00— report_created — created