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

Annotations only say this is a non-readonly, non-idempotent, non-destructive write. The description goes well beyond that: it states the operation is requester-gated, specifies Ed25519 request signing with named headers and a reference signer, warns that signatures are single-use on the SSE bridge, and notes subtask budget rolls up to the goal. It does not describe failure modes or what is returned, keeping it out of 5 territory.

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 purpose and hierarchy model are front-loaded in the first sentence, which is the most important content. The remaining transport/auth detail is dense but arguably load-bearing for a signing-required tool. Some of the transport exposition could be trimmed, but nothing is purely filler.

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 mutation tool with no output schema and nested-object params, the definition covers the two things an agent would most likely get wrong: the hierarchy semantics and the auth/transport signing contract. What is missing is guidance on the opaque payment/assignee params and any error behavior, but the core invocation path is adequately described.

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 only 43% (7 params, 3 described). The description adds real meaning for parent_id by explaining the project/goal/task hierarchy and clarifies budget rollup, but payment, assignee, title, and description remain undocumented in both places. It partially compensates for the coverage gap but leaves several parameters opaque.

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 names a specific operation (add a child node) and, more valuably, defines the resource semantics: a child of a project is a GOAL, of a goal is a TASK, of a task is a SUBTASK with unbounded depth. That makes the resulting node type predictable from parent_id. It does not, however, name or differentiate itself from siblings like set_node_parent or spin_out_node, so it stops short of a 5.

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?

Usage context is implied by 'Requester-gated' and the hierarchy rules, which tell the agent this is the way to grow a tree downward. But there is no explicit when-to-use vs alternatives guidance, and near-neighbors (set_node_parent, spin_out_node, set_hierarchy) are never mentioned, so routing must be inferred.

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