Reparent Node

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

Beyond the idempotentHint and openWorldHint annotations, the description reveals that the index must be in valid range (0 to parent's child count) and that omitting index appends. It also notes the output index behavior, adding useful context not in annotations.

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?

The description is very concise with three sentences. The main action is stated first, and the additional sentences provide essential details without wasted words.

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 the number of parameters, full schema coverage, annotations, and existence of an output schema, the description is largely complete. It covers the core behavior, though it could mention potential side effects or constraints (e.g., avoiding cycles).

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 no new semantic information beyond what the schema's parameter descriptions already provide for 'index' and the other parameters.

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 verb 'reparent' and the resource 'node', and distinguishes it from siblings like node_clone. It specifies the action: moving a node under a new parent with an optional index.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., node_clone, node_delete). It only mentions how to set the index but does not state prerequisites or conditions for use.

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