1. The paper does not discuss key work in visual CoT, in particular the two challenges that Zooming without Zooming: Region-to-Image Distillation for Fine-Grained Multimodal Perception (ICML 2026, hereafter ZwZ) raises against the "thinking with images" paradigm.
ZwZ makes two central arguments against tool-calling visual CoT methods such as DeepEyes. Both bear directly on this paper's premise, yet the paper neither cites nor discusses ZwZ:
- Inference cost. Tool-calling methods require multi-turn interaction and repeated re-encoding of images; ZwZ reports that its single-forward-pass inference is about 10× faster than agentic baselines. The policy in this paper makes up to 5 tool calls with a generation limit of 20K tokens, yet the paper reports no inference latency or token cost at all. If accuracy is comparable, choosing a paradigm that costs several times more requires additional justification.
- Source of the gains. ZwZ argues that the gains of visual CoT come mainly from CoT and RL (GRPO/DAPO) themselves, and have little to do with acquiring new visual evidence at inference time. Its Table 10 shows that DeepEyes loses only 2.0 points on average when tools are disabled and it answers directly (74.4 → 72.4), and Thyme loses only 0.6 points (74.0 → 73.4). In its Table 3, text-only RL without tools on the DeepEyes training data already brings Qwen3-VL-8B to 88.5 / 84.8 / 80.1 on V* / HR-4K / HR-8K.
This challenge is especially important for this paper, since its central claim is precisely to reward the visual evidence produced by tools. Yet on the same backbone, Qwen3-VL-8B, BiVER (Appendix D) reaches 93.2 / 81.4 / 81.6 on V* / HR-4K / HR-8K (average 85.4), while ZwZ-8B, which uses no tools and a single forward pass, reaches 91.1 / 84.4 / 82.0 (average 85.8). On HR-4K, BiVER is even below the "DeepEyes data + tool-free RL" result above. Although evaluation settings differ across papers (e.g., this paper reports 68.1 for the Qwen3-VL-8B base on HR-8K, whereas ZwZ reports 74.6), these results still indicate that, after introducing six tools, a process reward, and multi-turn calls, BiVER's advantage over text-only RL is unclear.
Moreover, the paper lacks the key experiment for separating the two sources of gains: how much does the trained BiVER drop when tools are disabled and it answers directly? If the drop is similar to that of DeepEyes, the process reward more likely improves the policy's own reasoning rather than its ability to acquire evidence with tools, which would undermine the paper's core narrative.
2. Averaging scores within a trajectory penalizes exploration and composition, undermining the very purpose of active visual search.
The paper averages the scores of all tool outputs in a trajectory, motivated by avoiding "more calls, more reward." However, by Eq. (7) in Appendix A, appending a new output lowers the trajectory score whenever that output scores below the current mean. Consequently, a trajectory that first crops the wrong region and then the right one receives a strictly lower process score than one that crops correctly on the first try, even when both answer correctly and have exactly the same R_base. After within-group z-scoring, this gap translates directly into a gap in advantage.
In search tasks, "it is not here" is itself useful information: ruling out wrong regions is a normal part of multi-step visual search (the setting targeted by, e.g., Mini-o3 and Visual Probe). Under this paper's setup, however, the evaluator sees only a single tool output image, so such exclusion calls necessarily receive low scores, and this kind of exploration is systematically penalized. As a result, the policy is pushed toward finding exactly the right image at every step. But if the model can localize the evidence precisely on its first call, it most likely already knows where the answer is without calling any tool, so what difference remains between such "search" and no search at all? The point of active visual search is precisely to allow trial and error and to converge to the evidence through it, and the current reward design runs counter to this.
The authors' own case study illustrates this tension. In the "rotate 270°, then zoom in" trajectory of Figure 5, the output of the first rotation is the full page, on which the target text is too small, so its support for the answer is likely low and it pulls down the trajectory mean. In other words, the success case the paper uses to showcase tool composition belongs exactly to the kind of trajectory that this aggregation is likely to penalize. The paper explicitly states that the mean gives no unconditional reward for more calls, but does not discuss that it also penalizes conditional, necessary calls.
A more reasonable design would adapt the process reward to question difficulty. For easy questions, where a single precise crop (or even no tool call) suffices, rewarding precise and concise calls is reasonable. For hard questions, however, the location of the evidence is itself uncertain and multi-step exploration is necessary; intermediate "misses" should not be penalized across the board as they are now, but trial and error should be tolerated and the process that eventually converges to the correct evidence should be rewarded. Requiring every step to be correct may be harmless on easy questions, but on hard questions that truly require search, it suppresses exactly the capability the model needs most.
3. The improvements over baselines are limited, and because in-distribution training data is added, it is hard to tell whether the gains come from data or from the algorithm.
Compared with the most relevant baselines, BiVER's advantage is small. On the high-resolution benchmarks, its average is only 2.0 points above ToolsRL (82.5 vs. 80.5), and it is below ToolsRL on V* (91.1 vs. 92.5). On the document/chart benchmarks, its average is only 1.9 points above DeepEyes* (61.6 vs. 59.7), and it is below DeepEyes* on InfoVQA-RF (58.1 vs. 59.7).
More importantly, these comparisons are confounded by differences in training data. Compared with DeepEyes, the paper adds 3,000 DocVQA samples, 70% of which are rotated or flipped, while the evaluation sets DocVQA-RF / InfoVQA-RF are constructed by the authors in the same way (70% rotated/flipped). That is, the training data contains samples from the same distribution as the evaluation, whereas DeepEyes* uses neither this data nor any tool other than zoom-in. Therefore, the largest improvement in Table 2 (5.0 points over DeepEyes* on DocVQA-RF) cannot be attributed to in-distribution data, the larger tool set, or the proposed reward. The tool-set ablation is similarly confounded: as the authors acknowledge, the no-tool configuration also changes the reward.
The only comparison that fixes both data and tool set and varies only the reward is Figure 4 (right): the average over seven benchmarks rises from 68.6 (outcome-only) to 70.6 (BiVER), a gain of only 2.0 points. Adding alignment or utility alone yields gains of only 0.4 and 0.6 points respectively, and on HR-Bench 4K/8K either direction alone is worse than outcome-only. Overall, the current experiments do not show that BiVER's gains come mainly from the proposed bidirectional visual evidence reward rather than from changes in data scale and distribution.
We thank the reviewer for the positive assessment and constructive suggestions. BiVER aggregates scalar scores (the mean of s_Q and s_A over the tool outputs of a trajectory), not embeddings; the aggregate is standardized within each GRPO group and added to the outcome reward (Eq. 5).
Table R1: Scores at the two ends of the candidate range (VizWiz, averaged over 1,769 examples; each tool output is scored in isolation).
The three intermediate conditions (Self / Center / Corner, at 61.21 / 48.39 / 34.08 crop-only VQA) interpolate monotonically in both scores. The two directions thus move together on average; their complementarity shows up on individual examples:
Table R2: Real cases where s_Q and s_A disagree
With s_Q alone the first case would be rewarded despite being insufficient for the answer, and with s_A alone the second would be mistaken for useful evidence; only their combination rewards tool outputs that are both question-directed and answer-sufficient. This is consistent with the reward ablation (Fig. 4, right): averaged over the seven benchmarks, S_Q only reaches 69.0 and S_A only 69.2, while their combination reaches 70.6.
The evaluator receives no reasoning text, tool name, arguments, or final answer, and all trajectories within a group share the same question, so differences in Z_i within a group arise solely from differences in the returned images. Over our full training run, 42.6% of groups have identical outcome rewards across all their rollouts (zero outcome advantage, hence no gradient), and 88.8% of those receive a non-zero BiVER signal — that is, for 37.8% of all groups the gradient comes solely from the quality of the tool outputs. Consistently, the mean s_Q of the policy's own tool outputs rises steadily from −1.33 early in training to about 0.06 later on.
We deliberately use a frozen copy of the initial policy as the evaluator: the gains then cannot be attributed to distillation from a stronger teacher, and a frozen evaluator cannot be exploited through self-reinforcing drift. Its task is also easier than the policy's — it only needs to rank tool outputs within a group, from a single already-focused image. The same construction yields consistent gains on Qwen3-VL-4B/8B (Appendix E).
Table R3: Frozen evaluators compared (500 VizWiz examples, paired; both measured against the same fixed crop-only VQA labels; best-of-N selects among Self / Center / Corner / Blank, Self baseline 64.12).
Within-group ranking ability thus depends little on evaluator scale: the 7B self-evaluator matches the 32B model on answer utility (92.4 vs. 91.9), and the 32B model's edge on question alignment (+2.3) is not large enough to be conclusive at 500 examples. The self-evaluator therefore already provides the discrimination needed for within-group ranking; a stronger evaluator is a plug-in component orthogonal to the method, which we will discuss as future work.
We hope these clarifications address the reviewer's concerns, and we would be glad to answer any further questions.