Pasting the whole document into the prompt is not context engineering
A team's answer to give the model context was to paste the entire manual on every call. It was slow, expensive, and it diluted the passage that actually mattered.
Pasting the whole document into the prompt is not context engineering
A solutions architect at a manufacturing company described their approach to giving the model context, and he was a little proud of how simple it was. The feature answered questions about a large product manual. So on every call, they pasted the entire manual into the prompt. The model had everything. What could be missing?
The feature was slow, expensive, and often wrong about things the manual explained clearly.
Everything is not the same as the right thing
The logic seemed airtight. The answer to any question is somewhere in the manual, so include the whole manual and the answer is always available. But a language model answering a question does not benefit from having a hundred pages in front of it. It benefits from having the right paragraph. The other ninety-nine pages are not help. They are noise the model has to see past to find the passage that matters.
So the feature struggled. The relevant section was in there, drowned among everything else, and the model sometimes latched onto a nearby passage that looked related and was not. Every call sent the full document, so every call was slow and every call was expensive, in direct proportion to the size of a manual that mostly had nothing to do with the question being asked. The team had maximized volume and called it context.
Volume was the problem, not the solution.
Context engineering is selection and structure
Giving a model context is a design task, and the task is choosing what to give it. The goal is to get the passage that answers the question in front of the model, clearly, with as little competing material around it as possible. That means selecting the relevant slice and structuring it so the model can use it. Pasting the whole document skips the actual work and hands the model the job of finding the needle, which is the one thing you were supposed to do for it.
Doing the work well tends to look like this.
- Retrieve the relevant slice. Pull the sections that actually bear on the question instead of sending the whole document every time.
- Chunk the source sensibly. Break the document into passages that stand on their own, so the piece you retrieve is coherent.
- Structure what you include. Label sections, keep related material together, and make it easy for the model to tell what it is looking at.
- Send less, not more. A focused, relevant context beats a giant one, and it is cheaper and faster at the same time.
- Check what actually got included. For a wrong answer, look at whether the passage that held the answer was even in the context, before touching the prompt.
The shift is from maximizing how much you include to being deliberate about what you include and how. That is the whole discipline. Retrieval and structure do what brute force cannot, and they cost less while doing it.
There is a threshold worth remembering here. AI features generally need something like 85 percent accuracy or better on their real data before they are dependable, and for a feature answering from documents, that bar applies first to whether the right passage makes it into the context at all. Pasting everything does not clear that bar. It just guarantees the right passage is present and buried.
How we approach it at Density Labs
In the AI Opportunity Assessment, our fixed two-week engagement priced at $2,500, a feature that pastes an entire document on every call is a pattern we see often, and it is usually the reason the feature is slow, costly, and unreliable at once. We treat context as something to select and structure, not maximize. We look at how the source is chunked, what actually gets retrieved for a real question, and whether the relevant passage arrives clean or buried. Fixing that is often cheaper than a quarter of prompt tuning, because the prompt was never the problem.
Giving the model context is a choice about what to include, not a decision to include everything. Select the slice, structure it, and let the model work on the passage that matters.
Context engineering is choosing the right page, not shipping the whole book.