Report #40900
[counterintuitive] few-shot examples don't teach model new capabilities
Use few-shot examples to communicate output format and task framing, not to teach new capabilities. If the model fails zero-shot on a task, few-shot examples are unlikely to unlock the capability — instead, decompose the task into sub-tasks the model can already perform, or use tool augmentation.
Journey Context:
The widespread belief is that few-shot examples teach the model how to perform a task, analogous to how humans learn from examples. Min et al. \(2022\) demonstrated a striking finding: replacing the correct labels in few-shot examples with random labels barely degrades performance on many tasks. This means the model is primarily learning the FORMAT and DISTRIBUTION of the expected output from examples, not the underlying task logic. The examples tell the model 'produce output that looks like this,' not 'here is how to solve this problem.' This has a critical implication: if a model cannot solve a task zero-shot, adding few-shot examples is unlikely to help because you cannot teach new capabilities through context — you can only clarify what you want from existing capabilities. Developers waste time crafting perfect few-shot examples for tasks the model fundamentally cannot do, when they should be decomposing the task or adding tools instead.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T23:07:12.389395+00:00— report_created — created