All articles
Your AI Is Not Hallucinating Because It Knows Too Little. You Might Be Giving It Too Much.
Prompt Engineering

Your AI Is Not Hallucinating Because It Knows Too Little. You Might Be Giving It Too Much.

Javier Echeverria··6 min read
Prompt EngineeringTokensOpenAI

When an AI model gives you an incorrect answer, the obvious reaction is usually to give it more information. You add another document, include the previous conversation, paste additional background, and perhaps explain the problem in greater detail. The reasoning seems straightforward: if the model was wrong because it did not know enough, giving it more information should help.

Sometimes it does. However, there are situations where adding more information can actually make the problem harder, particularly when the additional context is poorly organized, only loosely related to the question, or simply too large for the model to process efficiently. Recent research has raised an even more uncomfortable possibility: in some circumstances, language models can hallucinate more frequently as the amount of information they receive increases.

More Context Is Not the Same as More Understanding

An AI model does not process a large prompt in exactly the same way a person would read a well-organized research document. When you provide additional text, that information becomes part of the model's context, but the model still has to determine which parts are relevant to the task.

This distinction matters because a longer prompt can contain several different types of information at the same time. Some of it may directly answer the question, some may provide useful background, and some may have nothing to do with the final response. If all of it is presented together without a clear structure, the model has more material to consider without necessarily having a better understanding of what matters most.

That is one reason prompt length alone is a poor measure of prompt quality. A 10,000-token prompt can contain considerably less useful information than a carefully written 2,000-token prompt if most of those additional tokens are irrelevant.

Hallucinations Are Not Just a Knowledge Problem

The term "hallucination" is generally used to describe situations where an AI model produces information that sounds convincing but is incorrect, unsupported, or fabricated. It is tempting to assume that these mistakes happen because the model simply does not have enough information, but the problem is more complicated than that.

A model can have access to a large amount of information and still produce an incorrect answer. In some cases, the difficulty is not finding information but determining which information should influence the response. This becomes particularly challenging when a prompt contains conflicting sources, repeated information, ambiguous instructions, or large amounts of material that are only indirectly related to the question.

A Reuters analysis published in April 2026 highlighted this problem when discussing new experiments on how language models behave with increasingly large inputs. The analysis reported that hallucination rates increased for several models as the amount of information provided to them grew, with some models performing substantially worse when working with very large inputs. Reuters' analysis of AI hallucinations and larger inputs

The finding is particularly interesting because it challenges one of the most common assumptions about long-context AI: that giving the model more information will naturally make its answers more reliable.

The Problem With Giving the Model Everything

Imagine that you are asking an AI assistant to answer a question about a company's financial performance. You have a recent annual report, three older quarterly reports, a collection of press releases, several analyst summaries, and a long conversation about the company.

You could put all of it into one prompt and ask the model to figure out the answer. The model may technically be capable of processing all of that information, but you have also created several opportunities for confusion. Older figures may conflict with newer ones, analyst opinions may be mixed with official information, and the model now has to determine which sources should carry the most weight.

A better approach would be to identify the information that actually answers the question and organize it accordingly. If the user is asking about the latest quarterly revenue, for example, the most recent official filing should probably be more important than a comment made in an older report.

The difference is not simply the amount of information provided. It is the quality and relevance of the context.

Longer Prompts Also Cost More

There is a practical reason to avoid unnecessary information that has nothing to do with hallucinations: every additional piece of text can increase your token usage.

For AI applications that use APIs, input tokens are part of the cost calculation. If your application sends a 500-token prompt instead of a 5,000-token prompt, the difference may be insignificant for a single request. When that request is repeated thousands or millions of times, however, the additional tokens can become a meaningful part of the application's operating cost.

This is particularly easy to overlook when building conversational applications. A developer may add more instructions to a system prompt, include more conversation history, and attach more documents because each addition seems helpful in isolation. Eventually, however, the model is receiving a large amount of information for every request, much of which may no longer be relevant.

That is why token optimization and prompt quality are closely connected. Reducing unnecessary context is not simply about saving money; it can also make it easier for the model to identify the information that actually matters.

You Should Know How Big Your Prompt Really Is

One of the simplest improvements you can make is to stop guessing how large your prompts are.

Developers often estimate token usage based on word count, characters, or the number of paragraphs in a prompt. Those estimates can be useful for rough planning, but they are not reliable enough when you are trying to understand the actual size of a request. Different models can tokenize the same text differently, particularly when prompts contain code, numbers, formatting, or languages other than English.

Before sending a large prompt to an AI model, you can check its actual token usage with the Prompt Toolbox Token Counter. Seeing the token count makes it much easier to understand how much information you are actually giving the model and whether a prompt is becoming unnecessarily large.

This is especially useful when testing system prompts. A system instruction that seems reasonably short when you read it on the page can become surprisingly expensive when it is included in every API request.

More Information Can Still Be the Right Answer

None of this means that you should deliberately make your prompts as short as possible. There are plenty of situations where additional information genuinely improves the result.

A developer working with a large codebase may need to provide multiple files because the relationship between them is important. A researcher may need to compare several documents to identify contradictions or common themes. A customer-support system may need access to a user's previous interactions because the current question depends on something discussed earlier.

The important distinction is whether the additional information serves a purpose. If the model needs ten documents to answer the question, giving it ten documents makes sense. If it only needs two paragraphs but receives ten documents because "more context is better," the extra information may not provide any benefit.

In other words, the goal should not be minimum context. It should be relevant context.

The Better Way to Build a Prompt

A useful prompt generally has a clear hierarchy. Start by explaining what the model needs to accomplish, then provide the information it needs to complete that task, and finally clarify any constraints that should influence the response.

This structure makes it easier to distinguish instructions from reference material. It also reduces the chance that an important requirement gets buried underneath several pages of background information.

When working with multiple sources, it can also help to label them clearly and indicate which sources should be treated as authoritative. If one document contains the latest information while another is historical, saying so explicitly removes some of the ambiguity that the model would otherwise have to resolve itself.

The same principle applies to conversation history. Instead of assuming that every previous message remains equally important, applications can summarize older exchanges and retain the information that is still relevant to the current task.

AI Does Not Need Everything You Know

The temptation to keep adding context is understandable. When an AI gives an incorrect answer, providing additional information feels like the safest response because it seems to remove uncertainty. In practice, however, information only helps when the model can distinguish useful information from everything else.

As AI models become capable of handling larger and larger contexts, this distinction will become even more important. Bigger context windows give developers more flexibility, but they do not remove the need for good prompt design.

The most effective prompt is therefore not necessarily the longest one, and it is not necessarily the shortest one either. It is the one that gives the model the right information, in the right structure, at the right level of detail.

More information can make an AI system more capable. But when that information is irrelevant, repetitive, or poorly organized, adding more of it may simply give the model more opportunities to get confused.

Try the tools

Keep reading