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

Annotations establish a non-destructive, non-idempotent write. The description adds a genuine behavioral fact beyond them: parent and linkedNodes are populated automatically, so the caller need not supply them. It says nothing about duplicate-id handling or failure modes.

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 is front-loaded in the first clause, then the node shape follows. It is dense but every sentence carries information; the trailing lists/tables note is somewhat compressible but earns its place as a usage example.

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 a nested free-form object and no output schema, the description covers the node shape and auto-set fields, which is the main need. It stops short on lifecycle concerns (id collisions, ordering effects) and enumerates only a couple of the many node types an agent might need.

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 the baseline is 3, but the description does real work here by spelling out the otherwise opaque shape of the `node` object (type.resolvedName, isCanvas, props, nodes) that the schema only gestures at. It also illustrates list/table Containers, adding meaning the schema does not carry.

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 and resource ('Insert one node under an existing parent'), and the singular scope is clear. It does not explicitly distinguish itself from the sibling add_nodes, so an agent must infer the singular/plural split rather than being told.

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?

No when-to-use or when-not-to-use guidance is given. The only routing is an incidental pointer to get_style_reference for modifier setup; alternatives such as add_nodes or move_node are never mentioned, leaving selection to inference.

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