- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduces VESTA, a framework for training stateful tool-use agents with execution-derived supervision. Starting from API specifications, VESTA constructs replay-validated executable environments and workflow skeletons, then records reference tool calls and normalized pre/post states as state-transition contracts. These contracts are reused for SFT trajectory selection, RL rewards, and policy-conditioned RL task selection. The authors retain 131 environments, train Qwen3 models, and evaluate on three tool-use benchmarks. VESTA improves all 9 model–benchmark averages over the corresponding base models and generally outperforms EnvScaler and AWM, although those baseline comparisons are not fully controlled.
Critical strengths
- Reusable execution-grounded supervision. VESTA derives tool calls and state transitions from executable workflows and reuses them for SFT selection, RL rewards, and task sampling. The RL reward combines tool-call matching with state verification and guards against unintended state changes. And evaluations on three model sizes and three benchmarks validate the effectiveness and corresponding designs.
Critical weaknesses
-
The novelty and effectiveness of the proposed design are not sufficiently established. Stateful executable environment construction and task synthesis have already been explored in prior work such as EnvScaler, ScaleEnv, AgentWord and EnvFactory, while the paper does not clearly articulate what is fundamentally new beyond these pipelines. The main additional component—matching predicted tool calls against a single reference sequence alongside state verification—is also not fully convincing, since valid tool-use trajectories are often non-unique and a single reference may unnecessarily restrict RL exploration. A clearer comparison with prior methods and stronger motivation/ablation of this design are needed. Also, the authors only compare with AWM and EnvScaler in their experiments, without comparing ScaleEnv, AgentWord and EnvFactory, which should also be very related work and have already been revealed in their introduction.
-
The presentation and technical specification need improvement. The current figures are overly tuple-heavy and make it difficult to identify the paper’s unique contributions. The use of “offline” and “online” rollout is also potentially misleading, as the main distinction appears to be whether a user simulator is involved rather than the conventional meaning of online learning. In addition, important implementation details—such as how predicted and reference tool calls are aligned before computing multiset F1—are underspecified.
Questions for authors
-
What is the key technical novelty of VESTA relative to EnvScaler, ScaleEnv, EnvFactory, and other executable-environment construction pipelines? Please provide a more explicit component-level comparison and clarify which parts of the performance gains can be attributed specifically to the proposed state-transition contracts rather than the broader environment/task-generation pipeline.
-
How sensitive is the method to using a single reference tool-call sequence? Since multiple tool-call trajectories may be valid for the same task, can the authors compare reference-call matching against multiple-reference matching, or a less restrictive trajectory-level criterion?
-
How are predicted tool calls matched to reference calls when computing multiset F1, especially when there are repeated calls, reordered operations, or multiple semantically equivalent argument choices?
-
RL only seems not stable according to Tab 3. Can you provide more detailed analysis on it?