- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
This paper introduces ViewCraft, a training-free framework that improves frozen multimodal agents by jointly evolving an executable evidence interface and the procedure used to interpret its outputs. The interface controls evidence selection, transformation, and presentation, while how to reason over that evidence is also specified. Optimization combines failure-guided proposals, visual replay, paired development evaluation, and interface projection. Useful visual changes from rejected joint proposals are retained for further refinement. Across 8 image, document, and video benchmarks, ViewCraft improves the average task score over direct inference by 6.1 points. Ablations and cross-executor experiments further examine component interactions and skill transfer.
Critical strengths
A well-motivated approach to multimodal agent improvement. The paper distinguishes between making relevant evidence available and interpreting it correctly. Jointly optimizing these two components is practically meaningful. Substantial experimental controls support the main result. The evaluation includes text-only and interface-only optimization, alternative search schedules, and adapted MPO and Dynamo baselines within a shared search space. The token-matched Direct and self-consistency controls also help establish that the gains are not explained simply by providing more input or sampling more answers (Tables 2~4).
Critical weaknesses
The comparison with related methods has a limited scope. For example, GEPA is not compared in the experiments. MPO and Dynamo are evaluated through adaptations to ViewCraft’s interface and evaluation protocol, while it establishes an advantage over those particular adaptations rather than over the complete original systems. A clearer account of which original capabilities are preserved or restricted would strengthen the comparative conclusions.
Questions for authors
- For the MPO and Dynamo baselines, which components of the original algorithms are retained, and which are changed to fit the shared interface? Could these adaptations materially affect their relative performance?
- What limitations do you anticipate when applying ViewCraft to smaller VLMs? In particular, could weaker evidence interpretation or self-diagnosis require a different division of work between the optimizer and executor?
- Could you provide further practical guidance on the performance–cost tradeoff, including deployment costs and search costs relative to the adapted baselines?