Report #58244
[counterintuitive] Adding more relevant context to the prompt makes answers worse not better
Be selective about context: include only the most relevant information; use retrieval with relevance thresholds rather than dumping all retrieved text into the prompt; test whether additional context actually improves performance on your specific task; fewer high-quality chunks often outperform many low-quality ones
Journey Context:
The common belief is that more context equals better answers. If 5 retrieved chunks are good, 20 must be better. Research shows this is often false: adding more context, even relevant context, can degrade performance due to attention dilution \(the model's finite attention is spread across more tokens, reducing focus on the most critical information\) and the lost-in-the-middle effect \(additional context pushes important information toward the middle\). RAG systems that retrieve k documents and stuff them all into the prompt often perform worse than systems that retrieve fewer, more targeted documents. The model has finite attention capacity per layer, and more context means each piece receives proportionally less attention. Optimal context length is task-dependent and often much shorter than developers assume. Quality and positioning of context matters more than quantity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T04:15:08.955200+00:00— report_created — created