Report #96957
[counterintuitive] Should I always add few-shot examples to prompts
Start with zero-shot with clear instructions. Add few-shot examples only when the task is highly ambiguous, requires a specific non-standard format, or zero-shot fails. Ensure examples are perfectly representative.
Journey Context:
Developers reflexively add few-shot examples. But with modern instruction-tuned models, few-shot can actually hurt performance if the examples are slightly off-distribution, introduce bias, or confuse the model's internalized instruction-following capabilities. The model can overfit to the specific few-shot examples rather than generalizing from the instruction, leading to 'prompt drift'.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:19:39.777526+00:00— report_created — created