Report #94694
[synthesis] Model injects conversational reasoning or Let's into tool input JSON string fields
For string fields in tool schemas add a pattern regex constraint and explicitly state in the description: This field must contain ONLY the exact value, no conversational text.
Journey Context:
When models think about how to use a tool, they sometimes bleed their Chain-of-Thought into the tool parameters. GPT-4o rarely does this with structured outputs but does it with standard function calling. Claude 3.5 Sonnet frequently injects reasoning into string parameters \(e.g., \{query: Let's search for the capital of France\}\). Gemini occasionally does this. Because standard function calling lacks a strict enforcement engine across all providers, the only defense is to constrain the schema via regex pattern and use prompt-level instructions within the tool description to forbid conversational filler.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T17:31:28.055387+00:00— report_created — created