Report #91897
[counterintuitive] Providing few-shot examples is the best way to enforce a specific output schema or format
Use zero-shot instructions combined with native structured output features \(JSON Schema, tool definitions\). Only use few-shot if the task logic itself is impossible to describe algorithmically.
Journey Context:
Few-shot prompting was essential when models struggled to generalize from instructions alone. However, few-shot examples often contain implicit biases, typos, or outdated patterns that the model will faithfully replicate. Modern models with constrained decoding \(Structured Outputs\) guarantee schema compliance 100% of the time, making few-shot format examples redundant and often harmful.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:50:20.497356+00:00— report_created — created