GO TO A SECTION

↑ ↓ to navigate · Enter to openExplore all sections →
FDEInterviews logo
RecentarXiv preprint

Less Context, Better Agents: Efficient Context Engineering for Long-Horizon Tool-Using LLM Agents

A Dynamics 365 expense agent improves when old tool responses are pruned and summarized. Learn the controlled comparison, completion checks and limits of a five-turn window.

Breakdown by FDE Interviews · 9 min read · Updated

About the original · 2026
AUTHORS
Lodha, Varnosfaderani, Chakraborty, Mithal
FROM
Microsoft
PUBLISHED
Jun 2026 · arXiv preprint
IN THIS BREAKDOWN · 10 SECTIONS

You can read 17% of this breakdown.

01

The paper in one minute

An agent fills in an expense form, reads the updated balance and moves to the next item. Its conversation now contains several versions of the same form. Keeping every response preserves history, but also gives the model many outdated balances and control states to interpret.

This Microsoft study evaluates a simple context policy in Dynamics 365 Finance and Operations: retain recent tool interactions and summarize selected older ones. On the primary hotel-expense benchmark, pruning plus summarization improves the reported complete-itemization rate while reducing total tokens and wall-clock runtime relative to full history.

The comparison has an important boundary. The main configurations all include a separate user model that answers the agent's follow-up questions. A much weaker baseline omits that participant and often stalls. Its results cannot be used to attribute the entire improvement to context engineering.

The lesson is practical and narrow: a bounded working context can outperform a transcript containing stale operational state. The right window depends on the workflow, and a generated summary should never replace an authoritative read of balances, permissions or completed actions.

THE IDEA, VISUALLY
KEEP RECENT EVIDENCE; VERIFY THE BUSINESS STATE Illustrative context policy. Window sizes are configuration choices, not universal constants. Stable task + rules Older exchanges Summarize selected facts Recent complete turns Construct next input Task + bounded summary + recent tool results Next agent decision Fresh state read + deterministic checks A summary is a working note. It must not become the authority for balances, permissions or completed writes.
Our context-construction schematic separates working notes from authoritative business state. It adds explicit validation boundaries for deployment; those boundaries are recommendations, not a reproduced paper architecture.
Research notes: the problem, approach and results
50 tasks

primary hotel-expense benchmark, repeated over five runs

71.0 → 91.6%

reported full-context to pruning-plus-summary completion

62.7%

reported reduction in benchmark token use

THE PROBLEM

Verbose and outdated tool responses can overwhelm an agent's next decision.

THE IDEA

Keep recent complete tool exchanges and summarize selected evicted history.

THE RESULT

Expense itemization improves in the reported workflow while total tokens and benchmark runtime fall.

02

Why it matters to an FDE

Enterprise tools often return more information than the next decision needs: form metadata, navigation history, repeated records and full state snapshots. An agent can spend most of its inference budget rereading that material while still missing the latest relevant change.

This is a useful setting for context-window management. Measure whether the agent sees current state, retains unresolved requirements and knows when a write has actually succeeded. A shorter prompt is valuable only if those properties survive.

The paper also encourages an independent definition of completion. Reading the saved application state is stronger than trusting “done” in an assistant message. For a real financial workflow, extend that check to line identities, categories and exact amounts; a zero remaining total alone cannot establish that every item was classified correctly.

THE FULL BREAKDOWN

Understand the mechanism. Try it on a real problem.

Unlock this breakdown and 199 more papers.

Premium opens every paper in full, plus every answer, concept, course and guide on the site. One payment for six months of access.

6 months · One payment · No auto-renewal

Get Premium · ₹2,000 / $25
  • ◇1 architecture diagram
  • </>2 runnable code blocks
  • ▦3 results tables
  1. 03Key takeaways

    Six distinctions that keep context-pruning gains useful and prevent unsafe implementation shortcuts

    Free account
  2. 04How it works

    Follow recency pruning, summarization and the independent completion measurement

    Premium
  3. 05The numbers that matter

    Compare controlled configurations and separate workflow runtime from call latency

    Premium
  4. 06Try it yourself

    Test bounded retention with parallel tool calls and a counterexample to total-only validation

    Premium
  5. 07Where it breaks

    Recognize lost dependencies, summary errors and limits of the benchmark's completion metric

    Premium
  6. 08Using it on a deployment

    Pilot compaction with durable state, matched experiments and business acceptance checks

    Premium
  7. 09Interview angles

    Explain how to shorten an agent's context without losing the evidence needed for safe actions

    Premium
Back to the paper library →