- Rating
- 1(−1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
Trajectory2Gym is a training mechanism designed to improve student-model supervision by addressing two main challenges: composition coverage and decision grounding. The authors evaluate the method across five open-weight Qwen3 models and report strong performance on the τ-bench, τ²-bench, and BFCL benchmarks.
Critical strengths
The main advantage of the paper is its comparison against most open-weight model competitors and its evaluation on three major tool-calling benchmarks.
Critical weaknesses
I appreciate the authors’ effort and the overall direction of the work. However, I have several major concerns that I would appreciate the authors addressing.
-
My main concern is potential data contamination. The paper does not clearly explain which task sets were used as the starting point for generating the training trajectories. In Appendix A.2, the authors state that “BFCL follows its released training-side and evaluation membership.” However, to my knowledge, BFCL does not provide a standard public training split corresponding to its evaluation benchmark. The authors should therefore clarify exactly which BFCL tasks were used for training, where these tasks came from, and how they were separated from the evaluation set. The situation is also unclear for τ-bench and τ²-bench. For τ-bench Retail, the authors appear to use the training split released by the benchmark authors. However, for the Airline domain, the paper indicates that 50 airline tasks were used, and these appear to come from the benchmark evaluation tasks. If this interpretation is correct, the model may effectively have been trained on part of the test set. I have a similar concern regarding τ²-bench. The paper refers to a τ²-bench training set, but after carefully reviewing the benchmark, I could not identify an independently constructed training dataset. Instead, it appears that benchmark tasks may have been partitioned or adapted into smaller subsets. If the training and evaluation tasks originate from the same underlying task pool, there may be substantial semantic or structural similarity between them. This is particularly concerning because many tasks in these environments are already highly similar in terms of user goals, tool sequences, and database states. As a result, training on tasks derived from the evaluation pool could significantly inflate performance. Because of this issue, I currently find it difficult to interpret the results in Table 2 as a fair comparison. Several competing methods were not trained on the benchmark evaluation tasks, while Trajectory2Gym may have access to tasks that overlap with or are derived from them. The authors should provide a precise description of the task-level train/test separation and ideally quantify task similarity or overlap between the training and evaluation sets.
-
The paper compares Trajectory2Gym against several recent synthetic data generation methods for which open-source models have been released. However, the experiments do not appear to use the original training task sets from these methods to isolate the contribution of Trajectory2Gym itself. I suggest two controlled experiments. First, the authors could use the AReaL [1] training tasks as a fixed task set and generate training trajectories from exactly the same tasks using the original or standard trajectory generation procedure without Trajectory2Gym and the proposed Trajectory2Gym method. The resulting models could then be evaluated on τ²-bench and τ-bench. This would provide a much cleaner comparison because the underlying training tasks would remain fixed and only the trajectory construction or selection method would change. Second, the authors could use the Simia/τ training data as another fixed task source and repeat the same controlled experiment. Such experiments would provide stronger evidence that the gains come from Trajectory2Gym rather than differences in the underlying task distributions.
-
I respectfully disagree with the statement that trajectory quality is generally determined “by task completion or per-call execution.” I think this characterization is somewhat too broad. Some recent benchmarks already employ LLM-based judges to evaluate more nuanced aspects of agent behavior. For example, VITA-Bench uses LLM-based evaluation, and methods such as VULCAN [2] use LLM-as-a-judge signals for identifying and selecting higher-quality trajectories. More importantly, a failed task does not necessarily imply an incorrect agent trajectory. Given an initial state and a user request, the task may be inherently unsatisfiable, conflict with domain policies, or require the agent to refuse or explain that the requested action cannot be performed. In such cases, recognizing that no valid action should be taken can itself represent the correct behavior. Therefore, trajectory quality should not be defined only through whether the final user request was completed or whether individual tool calls succeeded. The paper would benefit from acknowledging these cases and distinguishing between task failure caused by incorrect agent behavior and task non-completion caused by an invalid, impossible, or policy-violating request.
-
Another concern is whether the reported improvements reflect genuine generalization or partial overfitting to the task distributions used during training. Given the concerns above regarding possible overlap between training and evaluation tasks, I believe an evaluation on harder out-of-distribution task sets would substantially strengthen the paper. In particular, I suggest evaluating the trained models on τ-Trait [3] and Thinking-Box [4]. These benchmarks use environments closely related to τ-bench-style tool-use settings but introduce more challenging task constructions and therefore provide a useful test of whether the learned behavior generalizes beyond the original benchmark distributions. Strong performance on these benchmarks would provide considerably stronger evidence that Trajectory2Gym improves general agent capabilities rather than primarily adapting models to the structure of the evaluation tasks.
-
AReaL [1] and VULCAN [2] are closely related to this work but are missing from the related work section. The authors should discuss both and clarify how Trajectory2Gym differs from them.
-
Figure 1 is not sufficiently clear.
-
The authors should clearly state which model is used as the user agent during trajectory generation and during evaluation on the τ benchmarks. They should also use the standard benchmark names consistently: “τ-bench” instead of “Tau1” and “τ²-bench” instead of “Tau2.”
References
[1] AReaL: https://arxiv.org/abs/2601.22607
Training data: https://huggingface.co/datasets/inclusionAI/AReaL-tau2-data
[2] VULCAN: https://openreview.net/forum?id=Ht4HB4pIQq¬eId=SS4dHupwle
Repository: https://github.com/microsoft/vulcan
[3] τ-Trait: https://arxiv.org/abs/2510.04491
Repository: https://github.com/collinear-ai/tau-trait/tree/main
[4] Thinking-Box: https://arxiv.org/abs/2608.19741
Questions for authors
Please read the weaknesses.