What they did
The study focuses on automated expense itemization in Microsoft Dynamics 365 Finance and Operations. They built a benchmark of 50 hotel expense tasks. They evaluate five GPT-5 configurations (including a no-user-model baseline) plus a cross-model test with Claude Sonnet 4.5. The key comparison is between full-context retention (baseline), pruning to last 5 tool call/response pairs, and pruning with summarization (summary window of 3). Results are averaged over 5 runs.
Key findings
- Full-context retention achieves 71.0% complete itemization but consumes 1,480,996 tokens and 14.56 hours per benchmark.
- Pruning to last 5 tool calls improves completion to 79.0% while reducing token use to 535,274 and runtime to 5.39 hours.
- Adding summarization to the pruned context further boosts completion to 91.6% and amount itemized to 99.64%, using 553,374 tokens and 5.79 hours.
- The no-user-model baseline achieves only 8.0% completion, highlighting the importance of the user model.
Why it matters
This work demonstrates that for tool-using agents, retaining full conversation history is not only costly but can hurt performance. Selective retention and compact summarization can improve both reliability and efficiency, offering a practical recipe for deploying enterprise agents at scale.
Caveats
The study is limited to a single domain (hotel expense itemization) and one enterprise system (D365 F&O). The benchmark size is modest (50 tasks). Results may not generalize to workflows with more diverse tool calls or longer horizons. The summarization method is not disclosed in detail; its performance may depend on the specific summarization technique.