Report #85711
[synthesis] Overfitting to happy-path tool schemas in few-shot examples
Include explicit 'negative examples' in few-shot prompts showing error responses and correct recovery patterns, not just successful executions; use 'what if' scenario training
Journey Context:
Developers typically provide few-shot examples showing perfect API calls and ideal JSON responses; the agent learns the 'shape' of success but has no model for handling 422 Unprocessable Entity or rate limit responses; when encountering errors, it hallucinates parameters like 'retry\_after' that don't exist or invents fallback URLs. The synthesis reveals that few-shot prompting creates an inductive bias toward success states; without explicit negative examples showing error schemas and recovery flows, agents cannot generalize to failure modes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:27:05.186230+00:00— report_created — created