Report #75448
[agent\_craft] Agent generates correct logic but wrong output format \(e.g., missing required JSON keys\)
For formatting tasks, provide 2-3 few-shot examples of the EXACT output structure within the system prompt rather than lengthy JSON Schema descriptions. For complex logic tasks, use schema validation with 'strict mode' instead of few-shots to avoid overfitting.
Journey Context:
OpenAI's best practices docs note that models are better at pattern matching from examples than parsing schema text. Few-shots anchor the token distribution to the right syntax, reducing format errors by ~30% in their evals. However, for code generation with complex requirements, few-shots can cause the model to hallucinate patterns from the examples that don't apply \(e.g., using example variable names\). The decision matrix is: if the task is syntactic \(JSON formatting, regex extraction\), use few-shots; if semantic \(algorithm design\), use strict schema with descriptions. This prevents the 'example memorization' trap where the agent outputs the example variables instead of the current context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:14:30.092007+00:00— report_created — created