- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
VideoRover trains a video agent to investigate questions through video cropping, image search, text search, and webpage browsing. Its central claim is that video observations guide retrieval while retrieved evidence can redirect subsequent video inspection. The work combines synthesized trajectories, SFT followed by GSPO, and a benchmark stratified by video duration and research difficulty. Experiments show substantial improvements over the backbone equipped with the same tools, but the methodological advance over closely related agents remains unclear, and the interpretation of the tool-use analyses extends beyond what their measurements establish.
Critical strengths
-
The improvement over the same backbone with tool access is substantial. Table 1 reports approximately 58% aggregate accuracy for VideoRover-RL versus 32% for the backbone in the agentic setting. This comparison supports the practical value of the training recipe more directly than comparisons against proprietary models answering without tools. RL also improves over SFT across every reported duration–difficulty subset.
-
The work provides a useful training and evaluation setup for an important task. Connecting sparse visual clues to external factual information is a realistic requirement for video agents. The synthesized trajectories and benchmark stratification provide infrastructure for studying this behavior. This supports the value of the work as a data and systems contribution.
Critical weaknesses
1. The methodological novelty is limited and insufficiently articulated.
The introduction characterizes existing approaches as keeping video reasoning and retrieval separate. However, VideoSearcher, already included as a baseline, combines temporal localization, spatial inspection, and multimodal web retrieval within a unified agent trajectory. Its interaction history accumulates both video and web observations, and it also uses SFT followed by RL. Consequently, a shared research state and the integration of visual and search tools are not, by themselves, a clear methodological departure.
Video-DeepResearch, which the manuscript cites, develops a closely related pipeline covering video grounding, visual search, text search, webpage visits, synthesized training trajectories, SFT followed by RL, and a dedicated benchmark. Its trajectory construction uses stage-wise tool unlocking, whereas VideoRover emphasizes flexible interleaving of video and retrieval actions. This is a potential distinction, but the paper needs to explain what specific policy or state-update design makes that interleaving a new mechanism beyond a general agent conditioned on interaction history. As written, I see an incremental combination of established components, with the clearest contributions being the data and task-specific training recipe.
2. The interpretation of the ablation and tool-use analyses should be narrowed.
In Section 6.4, the authors claim that VideoRover "does not follow a fixed tool-use pipeline" and adaptively selects actions based on each question's need for external knowledge. However, Figure 4 only reports average per-example tool-call counts across benchmark types. These aggregate statistics show differences in tool-use frequency but provide no evidence of action ordering or how intermediate observations influence subsequent actions. Therefore, Figure 4 does not substantiate the claim of adaptive tool use.
Appendix F provides qualitative examples of varying tool sequences and evidence-driven revisions, but these examples lack systematic quantitative analysis. They do not establish how frequently adaptive behavior occurs or how much it contributes to performance.
Similarly, Table 3 only evaluates the effect of removing individual tools on accuracy. While these results demonstrate the utility of the tools, they do not establish the flexibility or adaptivity of the tool-use strategy.
Overall, the current experiments lack direct evidence of adaptive tool-use behavior and fail to quantify its contribution to performance. More targeted analyses are needed to substantiate the claims in Section 6.4.
Questions for authors
-
What specific methodological contribution distinguishes VideoRover from VideoSearcher's unified interaction history and Video-DeepResearch's grounding-and-retrieval pipeline, beyond the tool interface, training data, and training recipe?
-
Is Section 6.4's conclusion about a non-fixed pipeline supported by evidence beyond Figure 4's average call counts? Please identify that evidence or clarify the intended scope of the conclusion.
3 comments
I thank the authors for their response and have decided to raise my score to 3.
Dear Reviewer aWSx,
Thank you very much for your recognition of our work and for raising your score. We sincerely appreciate your thoughtful review and constructive feedback.
Sincerely,
The Authors
Response to Reviewer aWSx
We sincerely thank the reviewer for the helpful review. We hope our replies below address your key concerns.
Thank you for raising this important concern. We agree that a shared interaction history and the integration of visual and retrieval tools alone do not distinguish VideoRover. Relative to VideoSearcher and Video-DeepResearch, our contribution centers on a knowledge-anchored data construction and training framework that enables an 8B model to coordinate dense segment-level video inspection with external research.
VideoSearcher constructs training data by adapting existing image–text QA pairs to videos retrieved using their entities. VideoRover instead starts from encyclopedia knowledge, grounds entities in videos, and generates questions linking visual evidence to external facts. While VideoSearcher already supports temporal refinement and multimodal retrieval, VideoRover emphasizes dense segment-level inspection and explicit webpage visitation. Video-DeepResearch uses stage-wise tool unlocking for trajectory construction and operates on at most 20 pre-extracted keyframes. Its frame selection and spatial cropping cannot recover temporal evidence omitted by this initial sampling. VideoRover can instead densely resample selected segments during research to inspect brief events and evidence across neighboring frames, particularly in long videos. We have added a brief discussion of these methods to the
Related Worksection. The results inTable 1further show that VideoRover achieves higher average accuracy than both methods.Beyond question construction, our trajectory synthesis permits flexible tool selection after initial video inspection, allowing intermediate observations to guide further video inspection, search refinement, or webpage verification. This concerns learning effective coordination rather than a new state-update rule. We test its benefit by retaining the same model, tools, and interaction limit while enforcing a repeated
crop_video → image_search → text_search → visitcycle with freely selected tool arguments.Performance decreases on VideoDR and all six VideoRover-Bench subsets, supporting the benefit of flexible coordination over this fixed pipeline, beyond access to the same tools. We have added this experiment to
Appendix F.Thank you for this important clarification. To examine action ordering directly, we additionally analyze all 300 trajectories from each model on VideoRover-Bench:
Each behavioral percentage denotes the proportion of trajectories exhibiting that pattern. Tool interfaces differ across models: Video-DeepResearch combines visual inspection with search, while VideoSearcher lacks independent webpage visitation. The third row counts a previously unused text query as the next action after a webpage visit.
Compared with the other two models, VideoRover more frequently returns to visual inspection after retrieval and, where webpage visitation is available, follows it with new search queries. These patterns are consistent with more flexible tool use according to current research needs, such as revisiting the video to locate relevant evidence or searching for additional information after inspecting retrieved sources. We have added this trajectory analysis to
Section 6.5.As detailed in
W1&Q1, enforcing a fixed tool cycle with the same model, tools, and interaction limit reduces performance across both benchmarks. Together, these results support non-fixed tool scheduling and its practical benefit over the tested fixed pipeline.