node_relocate

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

Discloses that body is flat, the mutual exclusivity constraint, and the idempotent nature (matching annotations). No contradictions with 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?

Two sentences with no wasted words. Key information is front-loaded: action, positioning options, and constraint. Very 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?

Covers all necessary aspects: action, parameters, constraints, and idempotency. No output schema, but description adequately addresses the tool's behavior.

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?

Adds meaning beyond schema by explaining each positioning option's effect (before, after, parent_node_id) and the mutual exclusivity rule. With 80% schema coverage, this extra context is valuable.

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?

Clearly states it relocates a node to a precise position relative to a sibling or to first slot under a new parent. Includes HTTP endpoint and differentiates from sibling node_move by specifying precise 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?

Explicitly instructs to supply exactly one positioning parameter and warns that handler rejects multiple. Does not explicitly compare to node_move, but the mutual exclusivity is well communicated.

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