W1. The gains over other tool-using agents are not convincing.
-
Same tools, mixed results. SpatialClaw uses the same perception models (Depth Anything 3 and SAM3; [1] App E.1), yet it beats HippoSpatial on SPAR-Bench with Qwen3.5-9B (55.4 vs 54.4) and GPT-5-mini (60.4 vs 59.8) (Tab 1). With Gemma-4-31B, SpatialClaw's own paper reports 51.3 on MMSI-Bench ([1] Tab 3), higher than the re-run here (49.9). It also reports 72.8 on MindCube, while the re-run gives 68.4 when Tab 1's per-setting scores are weighted by question count.
-
MindCube average. The MindCube Avg in Tab 1 is an unweighted mean of the three settings (App A.1), although Among makes up 86% of the questions and Rotation and Around only 5% and 9%. Weighting by question count, SpatialClaw is ahead of HippoSpatial with GPT-5-mini (73.4 vs 72.0), so the claim of the best MindCube result with all three backbones (Sec 4.2) depends on this choice. The MindCube paper and its official evaluation code report accuracy over all questions, as do pySpatial and SpatialClaw, so Tab 1's Avg departs from the standard metric and cannot be compared with published numbers.
-
pySpatial numbers do not match. With the same Gemma-4-31B backbone, Tab 1 gives pySpatial 54.2 on MMSI-Bench, while [1] Tab 3 reports 33.2 for its official code. The plain Gemma-4-31B scores in the two papers agree (37.2 here, 37.9 in [1] Tab 2), so the gap comes from how pySpatial was run. Sec 4.1 also does not say which perception models the re-run used (the original uses VGGT [2]).
-
Unclear source of the gain. No experiment gives the same five tools to an agent without the scene graph, so it is unclear whether the graph helps or the tools do, which are written for specific question types (e.g. the rotation tool for MindCube Rotation). The association thresholds were also picked on the MindCube test set (Tab 4), and changing them moves accuracy by about as much as the advantage over SpatialClaw.
-
Missing baselines. Think3D [3] is a training-free 3D-tool agent tested on MindCube. ConceptGraphs [4] and HOV-SG [5] already build 3D scene graphs from multiple views and query them with an LLM, which is the paper's core idea, and Coarse Correspondences [6] is a training-free multi-view method. None is cited or compared.
W2. The reported numbers do not match the stated setup or the released code, so the main results in Tab 1 cannot be verified.
-
MindCube counts. App A says the authors take 1,000 of MindCube's 21,154 questions in proportion to each setting, which gives 51 Rotation, 861 Among, and 88 Around questions (the released sampler gives the same). With 51 questions, a Rotation score must be a multiple of 1/51 (1.96 points). HippoSpatial's Rotation score with Qwen3.5-9B, 61.4, falls between them, and so do 74.0 and 71.8 for the other backbones. Overall, 21 of the 23 Rotation scores in Tab 1 are not possible with 51 questions, and 21 of the 23 Around scores are not possible with 88. The Rotation drops of 1.5 and 1.8 in Sec 4.3 are not possible either. It is unknown whether the scores come from fitting the full splits or averaging over several runs (but decoding is greedy as in App B so run variance should be low).
-
Coordinate frame. The rotation and camera-motion tools assume the z axis points up (App C, App H). The released code never aligns the reconstruction to gravity, and Depth Anything 3 returns poses in a camera frame where z points forward. When I ran the released tools on App H Example 3 in that frame, they put the correct answer on the wrong side and reported no turn for a 90 deg turn. The code also calls a function (model.infer) that the reconstruction libraries do not have. So the released code cannot have produced Tab 1, and any alignment step that was used is not described.
References
[1] SpatialClaw: Rethinking Action Interface for Agentic Spatial Reasoning, Cho et al., NeurIPS 26
[2] pySpatial: Generating 3D Visual Programs for Zero-Shot Spatial Reasoning, Luo et al., ICLR 26
[3] Think3D: Thinking with Space for Spatial Reasoning, Zhang et al., arXiv 26
[4] ConceptGraphs: Open-Vocabulary 3D Scene Graphs for Perception and Planning, Gu et al., ICRA 24
[5] Hierarchical Open-Vocabulary 3D Scene Graphs for Language-Grounded Robot Navigation, Werby et al., RSS 24
[6] Coarse Correspondences Boost Spatial-Temporal Reasoning in Multimodal Language Model, Liu et al., CVPR 25
We thank the reviewer for the feedback and address each point below.
Advantage with GPT-5-mini and SPAR-Bench variance. With GPT-5-mini, HippoSpatial still leads on MindCube (70.9 vs 67.5) and MMSI-Bench (55.4 vs 51.8). The SPAR-Bench gap is narrowest (59.8 vs 60.4) because stronger backbones already handle simpler spatial queries well, leaving less room for graph-based gains, a pattern visible across all methods and not only ours. The larger SPAR-Bench variance between Qwen and Gemma reflects SPAR's 20-task breadth, where model capacity plays a bigger role than on MindCube's narrower distribution.
Ablation definitions. W/o Strict Separation removes the boundary between the allocentric object store and the egocentric View Registry by merging them into a single joint representation. The drop is largest on subtasks requiring cross-view integration (Among −5.3 pts, Around −3.9 pts) and smallest on Rotation (−1.8 pts), directly supporting the design claim. W/o Pairwise Relations removes precomputed edges from the graph; the agent recovers partial information by calling tools over raw positions, leading to a smaller overall drop. We will add explicit definitions to the ablation caption in the revision.
Graph construction conditioned on the question. Object discovery uses the question and candidate answers to determine which objects to segment, so graph construction is question-conditioned by design. The graph is nonetheless fully fixed once Phase 2 begins and is never modified during reasoning. The description in Section 3.2 conflated graph construction with the subsequent reasoning phase; we will revise it to draw this boundary clearly.
Static objects and dynamic tasks. The motion questions in MMSI-Bench ask about camera movement between views (translation direction and rotation angle), not about objects physically moving across the scene. The
query_camera_motiontool handles these directly by reading camera pose pairs from the View Registry. No dynamic object tracking is needed, and none of the three evaluated benchmarks test scenarios where scene objects themselves move between frames.