How can irrelevant context hurt agent performance?

Irrelevant context can hurt agent performance because it adds information that does not help the current task and can make important signals harder for the agent to identify.

More context is not always better. Good agent systems try to provide the most useful information for the current decision rather than everything that is available.

Irrelevant context can distract the agent

Suppose an agent needs to decide whether a customer is eligible for a refund.

Useful context might include:

• purchase date
• refund policy
• order status
• payment method
• previous refund attempts

If the context also includes unrelated marketing history, old support conversations, unused product data, and irrelevant logs, the agent has more information to process without gaining anything useful.

This can make the important facts less prominent.

Important instructions can become diluted

Critical constraints should be easy to identify.

For example:

Important rule: Refunds above a certain amount require human approval.

If this rule is surrounded by a large amount of unrelated text, the model may give less attention to it than when the context is concise and focused.

This is sometimes described as context dilution.

Conflicting information can create confusion

Irrelevant context may also contain old or contradictory information.

For example:

Old context: Customer account is inactive.

Current state: Customer account has been reactivated.

If both remain in the prompt without clear ordering or authority, the agent may use the wrong fact.

Removing or replacing stale information reduces this risk.

Large context increases token usage

Every piece of text included in the model's context consumes tokens.

Unnecessary context can therefore increase:

• input token usage
• execution cost
• latency
• processing overhead

If the same unnecessary information is passed through many agent steps, the cost can accumulate significantly.

Irrelevant context can hide relevant evidence

Suppose a tool returns a response containing hundreds of fields, but only three fields matter for the next decision.

Passing the entire response may make it harder for the agent to focus on:

• status
• error code
• recommended next action

Extracting the useful fields produces a cleaner context.

It can increase the chance of using stale information

Long-running workflows can accumulate old observations.

For example:

Earlier in the workflow:

Inventory: Out of stock

Later:

Inventory: Restocked

If both versions remain in context without clear updates, the agent may make a decision using the outdated value.

Context should reflect the latest authoritative information.

It can reduce planning quality

An agent creating a plan should focus on information related to:

• the goal
• current state
• constraints
• dependencies
• available tools

Unrelated history can lead the model to introduce unnecessary steps or pursue irrelevant branches.

A focused context makes planning more aligned with the actual task.

It can make tool selection worse

If irrelevant details suggest unrelated actions, the agent may select the wrong tool.

For example, a customer-support workflow may include old billing information even though the current request is about delivery tracking.

The agent could mistakenly choose a billing tool instead of the shipping-status tool.

Keeping context task-specific reduces such mistakes.

Context-window limits make relevance even more important

Models have finite context windows.

If too much irrelevant information is included, useful information may:

• receive less attention
• be pushed farther away from the current instruction
• require aggressive truncation or summarization
• be excluded entirely

The available context window should therefore be treated as a limited resource.

Context should be selected, not accumulated blindly

A weak strategy is:

> Add every message, tool output, document, and state field forever.

A better strategy is to:

• keep current goals and constraints
• include relevant state
• add useful new observations
• summarize older history
• retrieve documents only when needed
• remove stale or unrelated details

This keeps the active context aligned with the current step.

Example

Suppose an agent must determine why an API call failed.

Useful context:

• request parameters
• response status
• error message
• latest retry result
• relevant API documentation

Irrelevant context:

• earlier unrelated API calls
• user profile details
• old deployment logs
• unrelated tool results

The smaller focused context gives the agent a clearer basis for diagnosis.

In short

Irrelevant context can reduce agent performance by distracting the model, diluting important instructions, introducing stale or conflicting information, increasing token cost, and making planning or tool selection less accurate.

Effective agent systems keep context focused on what is useful for the current decision instead of continuously accumulating everything that has happened.