- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper identifies a problem: when the context history of a GUI agent accumulates tool-using actions, the agent tends to invoke unnecessary tool calls. To quantify how severe this is, the authors build a paired benchmark that fixes the question and the state (screenshot) at a given point while switching only the history context. In both the synthetic (Main-S) and the external-benchmark-derived (External-R) settings, the first-response tool-attempt rate is higher after tool-trace histories than after matched action-free histories (T−N > 0) across all five LLMs. The paper also proposes mitigation strategies to alleviate unnecessary tool calling, both training-based and training-free.
Critical strengths
(1) The paper's experimental setting reflects the components of a GUI agent environment well.
(2) The experimental results appear reliable: the experiments were conducted in a controlled setting, and confidence intervals are reported.
Critical weaknesses
(1) The paper's central scenario is one in which the agent's history is filled with tool calls and the user then suddenly asks a simple question that does not require tools. It is unclear how often this happens in the real world. As an agent paper, it should better justify what real-world problems the defined issue can cause. To strengthen the justification, the authors should report how often such situations occur in practice.
(2) The benchmark consists of questions that the agent can answer directly without tools (short knowledge or calculation questions), but it is unclear what the criterion for this is and where it comes from. Figure 2's example, "What is 64 multiplied by 17?", appears to represent the benchmark's questions, yet in my view using a calculator is a reasonable choice for this question. The authors should clarify the criterion and show that it would be widely accepted.
(3) The related work shows that tool overuse is already a well-studied topic, so it is unclear what novelty these controlled-setting results offer over prior work. If there is novelty, the authors should state it clearly. To distinguish itself as an agent paper, the work should also present failure cases or problem scenarios from real-world deployment.
(4) The paper emphasizes that it is about GUI agents (the title begins with "GUI"), but no experiment tests whether the effect is specific to the image modality. For example, there is no text-only condition or screenshot-removed condition, so it is impossible to tell whether the effect stems from the GUI/visual context or is a general property of histories containing tool calls.
(5) In Section 7, the reward gives the lowest value whenever the agent attempts a tool call, so it is unsurprising that the agent stops calling tools. This is not really a mitigation: the trained agent may suffer a serious side effect, namely never calling tools even when they are necessary. The paper does not evaluate this on required-tool tasks for the RL model.
(6) The writing quality needs to be improved substantially.
Questions for authors
(1) As far as I understand, there are four channels through which the agent's tool attempt is detected (a native provider function call, a serialized tool-call block naming a tool, a standalone action-record line, and executable control code). Is there a specific reason for choosing these four?
(2) Could you also report the results in the H0 (no-history) setting? This would be useful for comparison.
Writing Suggestion: The three paragraphs in Related Work should be merged into two, as they contain a lot of redundant content. The space freed up this way could be used to expand Section 3. Section 3 is quite abstract, which makes the details hard to follow. Eq. 2 appears to be a key definition, so placing it in the appendix does not seem appropriate. Including more mathematical equations would make the method easier to present, and the inputs and outputs would be clearer than they are now.