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

No annotations are provided, so the description carries the full behavioral burden. It says it attaches to an existing node but doesn't disclose what happens if parentId is invalid, whether nodes can include nested children in one call, whether the operation is additive/non-destructive, or what the response contains.

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 tight sentences with the core action front-loaded followed by compact style rules. Little waste, though the emoji/depth conventions could be consolidated.

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 needed mutation tool with no annotations and no output schema, the description should cover failure modes and result shape. It covers content conventions but leaves parent validity, atomicity, and return behavior unaddressed, leaving meaningful gaps.

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 67% and the schema already documents text conventions (3-6 words, emoji) and projectId's URL trick; the description largely restates the text conventions. It adds no meaning for parentId or the nodes array structure beyond what the schema provides.

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?

States a specific verb (add) and resource (sub-branches/child concepts/sibling ideas) and pins the target (an existing node in the mind map). This clearly separates it from create_mindmap, update_node, and move_nodes without needing their schemas.

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 implies when to use it (attaching children to an existing node) but gives no explicit alternatives or exclusions—e.g., when to use update_node instead of adding, or whether nodes can be duplicated. The second sentence is style guidance, not usage routing.

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