Move / Reparent / Reorder Node

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

No annotations provided, so description carries full burden. It discloses behavioral traits: reparenting, promotion, reordering, and specific behavior for takes. Also mentions return value (new canonical handle) for stability.

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?

Three sentences with no filler. Front-loaded with action verb and resource. Every sentence adds essential context (usage rules, constraints, return value).

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?

Given 5 parameters (1 required) and no output schema, the description adequately explains all aspects: destination options, node type compatibilities, take special case, and return value. No further context needed from sibling tools.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the mutual exclusivity of destination parameters and elaborating on to_root behavior for takes, which goes beyond the schema.

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?

The description clearly states the tool reparents, promotes, or reorders nodes, specifying the resource types (objects, takes, render_data). It differentiates from siblings like remove_entity or clone_entity by focusing on movement operations.

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?

Explicitly states exactly one destination field must be provided (parent, before, after, to_root:true). Provides specific rules for takes (to_root reparents under Main, Main take cannot be moved) and notes siblings/parents must share the moved node's kind.

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