研究:工具输出改为检索后 GPT 模型准确率下降最多 11.3 分
Same Simulation, Different Evidence: Where Retrieved Tool Output Costs LLM Agents Accuracy
PHREEQC 模拟结果固定不变,只是让 GPT-5.2 按需检索报告就掉 9.4 分,原因是它改用自己的输出文件瞎舍入。Claude 系列反而没受影响,做 agent 上下文管理的值得对比看看。
arXiv 论文用 USGS 的地球化学模拟器 PHREEQC 构建 158 道执行验证的多选题,测试 agent 从上下文读取工具输出改为按需检索的代价。GPT-5.1 和 GPT-5.2 准确率分别下降 11.3 和 7.9 分,而 Claude Opus 4.6 与 Claude Sonnet 4.6 未检测到损失。重放全部 11,007 次模拟调用后发现,GPT 模型计算结果没变,问题是回答时跳过模拟器报告、改用自己更高精度的输出文件并错误舍入,作者称之为 evidence substitution。为 GPT 模型明确指定权威输出可将准确率提高 6.3-7.9 分。
Same Simulation, Different Evidence: Where Retrieved Tool Output Costs LLM Agents Accuracy
LLM agents that compute the right answer can still answer wrongly. Agent harnesses increasingly keep long tool outputs out of the context window, saving them to files that the agent searches or reads on demand. We ask where this costs accuracy with a real scientific tool: PHREEQC, a widely used geochemistry simulator from the USGS, whose reports reach 846.8k characters and whose determinism lets every printed value be traced. Agents use it to answer 158 execution-verified multiple-choice items. When agents read the simulator's report through a section index rather than in context, GPT-5.1 and GPT-5.2 lose 11.3 and 7.9 points of accuracy, while Claude Opus 4.6 and Claude Sonnet 4.6 show no detectable cost. Re-running all 11,007 logged simulator calls shows that both GPT models compute the keyed value about as often as before; what changes is the evidence they answer from. Under retrieval they often skip the report, answer from their own higher-precision output files, and misround to a neighboring option, a failure we call evidence substitution. With the simulation held fixed, retrieval still costs GPT-5.2 9.4 points. For GPT-5.4, more frequent correct simulations mask an evidence-use loss of about ten points, leaving a net change indistinguishable from zero. Naming the authoritative output raises accuracy by 6.3-7.9 points over plain retrieval for the three GPT models; for GPT-5.1 and GPT-5.2, inlining outputs that fit works as well, while asking for correct rounding does not. Context-management choices in agent harnesses should be judged by where accuracy is lost, not only by final accuracy.