subtree_snapshot

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructiveHint=true and readOnlyHint=false, but the description reads like a benign capture and never explains what is destructive — whether an existing snapshot handle is replaced, whether state is consumed, or what gets locked. The only behavioral additions are the "guarded/independent" constraint, the integrity-checked JSON option, and the restore-scope limitation; the destructive profile is left entirely unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the resource and scope front-loaded and no filler. It is jargon-heavy ("guarded independent FK subtree", "integrity-checked workspace JSON") and crams three distinct ideas together, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema, destructive-flagged tool, the definition omits the two things an agent most needs: what path writes and what makes the operation destructive. The restore-scope caveat helps, but the behavioral and parameter gaps leave the call under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry both parameters, and it only gestures at them: "optional integrity-checked workspace JSON" hints that path designates a JSON file, and "subtree" hints that root is a subtree root, but neither name is tied to a meaning and there is no indication of format or whether writes occur. The agent is left guessing at path's role.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

"Capture every stored local/global pose of a guarded independent FK subtree" gives a concrete verb (capture), a precise resource (all local/global poses within one FK subtree), and a scoping qualifier (guarded, independent). It is distinguishable from apply/restore siblings, but it never names the closest alternatives (subtree_pose_read, pose_snapshot, subtree_restore), so the differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit "use this when" statement, no prerequisite, and no named alternative. The clause "Other scene edits are outside its restore scope" is a scope caveat about the eventual restore, not guidance on when to snapshot versus read poses directly, so the agent must infer the workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.