Report #82947
[synthesis] Inconsistent markdown formatting in tool call string arguments across models
Always sanitize tool call arguments on the client side. Do not expect models to omit markdown formatting inside string parameters.
Journey Context:
When passing a string parameter \(e.g., code\_snippet\), GPT-4o frequently wraps the value in markdown code blocks even when explicitly told not to. Claude 3.5 Sonnet usually returns raw text but might add inline backticks. Gemini 1.5 Pro almost always returns raw text for strings. Because GPT-4o's behavior is deeply ingrained, regex stripping of markdown fences from string arguments is a mandatory post-processing step in any multi-model backend.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:49:17.067513+00:00— report_created — created