Report #93293
[synthesis] Error Erasure via Brittle Parsing
Use structured output generation \(e.g., JSON mode, function calling\) natively rather than regex-based parsing of free-text. If parsing fails, return a highly descriptive error message to the agent explicitly stating 'Your output was malformed. You forgot a quote. Try again,' rather than a generic 'Tool not found.'
Journey Context:
Agents sometimes output tool calls in slightly wrong formats \(e.g., missing a quote\). If the scaffolding uses brittle regex parsing, it fails silently and returns a generic error. The agent assumes the tool doesn't exist and switches to a suboptimal strategy, never realizing it just made a syntax error. The synthesis is that brittle parsing acts as an 'error-erasing layer.' It transforms the agent's syntax errors into environment errors, fundamentally altering the agent's internal causal model. The fix is to use robust parsing and, crucially, to reflect the exact parsing error back to the agent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:10:38.958694+00:00— report_created — created