- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
FlowTool presents a practical framework for tool-based image editing, with clear benefits in structured parameter prediction and inference efficiency. However, the methodological novelty is relatively limited, and the paper does not sufficiently establish that Flow Matching is preferable to simpler or alternative multimodal prediction methods for this task. The lack of controlled comparisons against strong continuous-output baselines is particularly important because it leaves the central methodological motivation insufficiently validated. Together with the remaining questions concerning synthetic instruction quality, reward robustness, and the interpretation of the efficiency results, these limitations weaken the case for acceptance.
Critical strengths
-
Clear presentation. The paper is generally well-structured and clearly presents the proposed framework, training pipeline, and experimental results, making the method relatively easy to follow.
-
Reasonable evaluation metrics. The evaluation uses a combination of reference-based metrics and reference-free assessments, providing complementary perspectives on image-editing quality and instruction following.
Critical weaknesses
-
Insufficient evidence for the necessity of Flow Matching. The central methodological claim is that conditional Flow Matching is a better formulation for continuous image-editing parameters than autoregressive generation. However, the current experiments do not isolate the contribution of Flow Matching from that of the structured output representation and task-specific training. In particular, the comparison between different ODE integration steps does not establish superiority over a properly tuned direct-regression model or other multimodal prediction approaches. The one-step variant is not necessarily a strong representative of these alternatives. Without such controlled comparisons, it remains unclear whether the observed gains arise from Flow Matching itself or primarily from replacing text-based outputs with a dedicated continuous prediction architecture.
-
Limited methodological novelty beyond existing components. The proposed framework combines a pretrained VLM, a DiT-based parameter generator, a tool-presence head, a two-stage supervised training curriculum, and reward-based post-training using an existing DiffusionNFT-style objective. While this integration is reasonable, the paper does not introduce a substantially new flow-matching objective or reinforcement-learning algorithm. The main contribution therefore appears to lie in task formulation and system integration. The paper would benefit from a clearer explanation of what generalizable methodological insight it provides beyond applying existing generative modeling and post-training techniques to a new output space.
-
Potential limitations in data construction and generalization. The training corpus contains approximately 497K examples derived from internally curated expert edits, with user instructions synthesized by a pretrained VLM. The paper does not sufficiently characterize the fidelity of these synthetic instructions, the distribution of tool activations, or the diversity of editing styles. Moreover, the 300-example internal evaluation set provides limited evidence of generalization to real user instructions and out-of-distribution editing requests. It would be useful to evaluate instruction quality, report more detailed dataset statistics, and assess generalization under independently collected user prompts.
-
Reward design and efficiency claims require further validation. The post-training reward combines pixel-level similarity to an expert-edited target with a VLM-based instruction-following score. These objectives can conflict, and the reported gains from RL are not uniform across all metrics. Further reward ablations and independent evaluation would help establish the robustness of the improvement. In addition, the reported latency comparison mixes local inference time for FlowTool with end-to-end API response times for proprietary models. Although this distinction is disclosed, it prevents attributing the full latency gap to the proposed generation paradigm. Comparisons against controlled local baselines with matched hardware and inference boundaries would provide stronger evidence for the claimed efficiency advantage.
Questions for authors
Please refer to "Weaknesses" above.
5 comments
Official Response to Reviewer mnZo (2/2)
W3
W3. Potential limitations in data construction and generalization.
We would like to clarify that our evaluation already covers both in-distribution and out-of-distribution settings. FlowTool-Eval is the only in-distribution benchmark, consisting of held-out examples from our internal data collection. MMArt-Bench, ArtEdit-Bench, and MIT-Adobe5K are out-of-distribution benchmarks relative to FlowTool’s training dataset, constructed independently of our internal corpus. Overall, our whole evaluation set across 4 benchmarks consists of 1135 samples, in which 300 samples are in-distribution witht the training data, and the remaining 835 samples are entirely out of distribution. Our evidence of generalization therefore extends beyond the 300-example internal evaluation set: performance on these three external benchmarks supports transfer beyond the training-data distribution. In addition, we also added the user preference study in Appendix D of the revised manuscript, showing that FlowTool remains strong on human evaluation, in addition to reference-based metrics and VLM-as-a-judge evaluation.
We agree that a more detailed assessment of synthetic instruction quality and an evaluation using independently collected user prompts would strengthen the paper. However, manually verifying instructions and collecting and annotating new user requests require substantial annotation effort beyond the short rebuttal period. We plan to add these analyses in a subsequent revision, together with a more detailed discussion of instruction quality, subjecting to internal approval. Thank you for your suggestion.
W4
W4. Reward design and efficiency claims require further validation.
We used SC and L1 as reward to train our model with RL. Considering the 15 metrics across the three instruction-driven benchmarks evaluated with L1+SC rewards in Table 1, SC and the overall score improve across all three benchmarks, while both L1 and L2 improve significantly on FlowTool-Eval and ArtEdit-Bench. These results demonstrate that reference similarity and instruction alignment can improve jointly under our combined reward.
On MMArt-Bench, RL improves SC and the overall score, with only very small increases in L1 and L2. These minor declines in reference similarity accompany significant gains on the other two benchmarks. The decreases in PQ on FlowTool-Eval and ArtEdit-Bench are also negligible. Since the base model already achieves strong perceptual quality, we place greater emphasis on improving SC through RL, and the consistent SC gains demonstrate the effectiveness of this choice. Overall, these results support improved instruction alignment and overall editing quality while largely preserving perceptual quality.
Regarding latency, since the proprietary models cannot be deployed locally and we cannot access their server-side timing, we report end-to-end API response time as the accessible measure of their deployment latency, which we believe is the best alternative. Moreover, for locally deployable baselines (JarvisArt and RetouchIQ), we control the hardware, evaluation inputs, and timing scope: all models run on an NVIDIA A100, using the same 200 examples, with single-sample inference and latency measured for editing-plan generation. Under these conditions, FlowTool takes 0.19 seconds, compared with 32.11 seconds for JarvisArt and 30.36 seconds for RetouchIQ. Thus, our significant efficiency advantage is supported by a fair, controlled local comparisons and does not depend on API-related overheads. We believe provided a sufficiently strong enough evidence for our claimed efficiency advantage.
A Gentle Reminder
Dear Reviewer,
We really appreciate your constructive feedback, which has helped us significantly strengthen the manuscript.
As the rebuttal period is about to end, we would appreciate your thoughts on whether our responses and revisions have adequately addressed your concerns. If any questions remain, we would be happy to discuss them and provide further clarification.
Thank you again for your time and consideration.
Official Response to Reviewer mnZo (1/2)
We thank the reviewer for the thoughtful comments and suggestions. We have significantly revised and updated our paper with additional results and discussion. We address the reviewer's concerns as follows:
W1
We agree that evaluating different ODE integration steps does not replace a comparison with a separately trained direct-regression model. To address this concern, we train a deterministic regression model and an autoregressive model (both with Qwen3.5-4B backbone) with our curated training dataset (the same data used to train FlowTool). The regression comparison evaluates the benefit of flow matching over deterministic prediction, while the autoregressive comparison assesses whether the gains stem from our flow-based formulation rather than differences in training data.
MMArt = MMArt-Bench, FT-Eval = FlowTool-Eval, ArtEdit = ArtEdit-Bench.
The results show that FlowTool significantly outperforms the regression baseline despite both methods producing continuous editing parameters. This supports the benefit of flow-based parameter generation over the deterministic predictor, beyond the choice of a continuous output representation. FlowTool also substantially outperforms the autoregressive baseline, further supporting the contribution of our flow-based formulation beyond access to task-specific training data. These controlled ablations strengthen our empirical validation relative to JarvisArt and RetouchIQ, which, to our knowledge, do not report comparable experiments that hold training data fixed to distinguish the contribution of their modeling approaches from the benefits of their datasets. More details are available in Appendix C of the revised manuscript.
W2
We agree that FlowTool builds on established flow-matching and reinforcement-learning objectives; our contribution is not a new objective for either framework. Rather, it is a formulation of parameter-based tool use as conditional generative modeling over continuous editing parameters, together with the architectural and training choices needed to make this formulation effective. FlowTool can produce an editing plan through flow matching without autoregressive reasoning. We are the first to do this for image retouching, to the best of our knowledge, which position our work completely different from existing state-of-the-art works like JarvisArt, RetouchIQ, where they all use the same paradigm of finetuning MLLM for autoregressive parameter generation.
The central methodological insight is that multimodal understanding and executable parameter generation can be learned together without expressing the editing plan as an autoregressive language sequence. FlowTool models dependencies among continuous parameters during joint generation, while explicitly separating tool activation from parameter-value prediction. This distinction matters because predicting an appropriate value and deciding whether to activate the corresponding tool are different decisions. The tool-presence head and masked flow-matching objective encode this structure, and our ablation demonstrates the benefit of explicitly modeling activation.
The two-stage curriculum addresses a complementary optimization issue: adapting a pretrained VLM to a randomly initialized continuous generator. Our ablation supports first learning parameter generation under fixed multimodal representations, followed by joint adaptation. Together, these results provide evidence for the design choices underlying the formulation.
So overall, our novelty lies in distinctive problem formulation, adaptation of multiple flow-based techniques to image editing with tools (being the first to do so and successfully), and strong empirical effectiveness and efficiency compared to existing methods. In short, our approach is new, different and it performs much better than specialized MLLMs and competitively with frontier MLLMs, while remains much more efficient in model size and inference time.