Report #88620
[synthesis] Excessive conversational filler and unsolicited caveats when executing tool calls
For Claude, explicitly instruct in the system prompt: 'Do not add any conversational filler. Only output the tool call.' For GPT-4o, use the \`tool\_choice: 'required'\` or JSON mode to suppress chatter. For Gemini, enforce strict output parsing as it often wraps tool JSON in markdown.
Journey Context:
When using tool-driven agents, token efficiency is critical. Claude 3.5 Sonnet has a strong behavioral fingerprint of adding polite conversational text \('I will now search for...', 'Certainly\!'\) before or after tool calls, even when not explicitly requested. GPT-4o is generally more concise but might add caveats if the tool is destructive. Gemini often formats tool calls as markdown code blocks instead of raw JSON. A single agent architecture expecting clean JSON tool calls will break or waste tokens if it doesn't apply model-specific anti-chatter directives.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:20:14.693321+00:00— report_created — created