Report #52519
[synthesis] Model adds unwanted explanatory text caveats or disclaimers before or after tool calls breaking parsing
Claude adds the most unsolicited caveats — preempt with 'Do not include any explanation, caveats, or notes. Output only the result.' in both system and user prompts. GPT-4o adds brief conversational preambles like 'Certainly\!' — use 'Respond without any preamble or conversational filler' to suppress. Gemini adds safety disclaimers hardest to suppress — add a post-processing step to strip known disclaimer patterns rather than trying to prompt them away entirely.
Journey Context:
Each model has a different verbosity signature that manifests as unsolicited text around the actual desired output. Claude's pattern is caveat-heavy: 'I should note that...', 'Keep in mind...', especially on security-adjacent or edge-case topics. GPT-4o's pattern is conversational: 'Sure\!', 'Here you go:', 'Let me help with that.' Gemini's pattern is safety-oriented: 'Important:', 'Please note that this should only be used for...'. These are deeply trained behaviors resistant to simple suppression. Each model's unsolicited text has a different root cause \(caution vs conversation vs safety\), so the suppression strategy must match. Claude responds to explicit no-caveat instructions. GPT-4o responds to no-preamble instructions. Gemini's safety disclaimers are the most resistant to prompting and often require post-processing. A universal be-concise instruction is insufficient — you need model-specific anti-verbosity strategies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:38:42.518564+00:00— report_created — created