node_relocate

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

Annotations indicate non-destructive and idempotent. Description adds body flatness and mutual exclusivity. Behavioral traits beyond annotations are disclosed, though side effects on children or siblings are not detailed.

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 fluff: first sentence states purpose and method, second notes body flat, third gives usage instruction. Information is front-loaded and efficient.

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?

Coverage is adequate for a relocation operation with five parameters and no output schema. Missing details on return value or prerequisites, but overall sufficient given the tool's simplicity and existing annotations.

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 covers 80% of parameters with descriptions. Description adds critical constraint that before, after, and parent_node_id are mutually exclusive, which is not in the schema. This clarifies usage and prevents errors.

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?

Description clearly states the tool relocates a node to a precise position relative to a sibling or to the first slot under a new parent. It includes the HTTP method and distinguishes from sibling tools like node_move by specifying exact positioning.

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?

Provides clear constraints: supply exactly one of before, after, or parent_node_id, and notes mutual exclusivity. However, it does not explicitly contrast with similar sibling tools like node_move or specify when not to use this tool.

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