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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds useful behavioral context beyond that: parent and linkedNodes are automatically set, and lists/tables require specific Container props, which helps an agent invoke the tool correctly.

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 description is front-loaded with the core action, then compactly explains the node shape, automatic fields, and list/table special case. Every sentence contributes useful information without clutter.

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?

Given the rich schema, annotations covering mutation semantics, and a nested node object, the description supplies the critical node shape and automation behavior. It is complete enough to call correctly, though it could mention sibling alternatives for fuller context.

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 schema already documents all parameters. However, the description adds substantial meaning for the complex node parameter by sketching its expected shape and clarifying that parent and linkedNodes are managed automatically, going beyond the schema's terse 'Node definition' note.

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 clearly states the specific verb and resource: 'Insert one node under an existing parent.' It implies a single-node insertion, distinguishing it from a multi-node sibling like add_nodes, but it does not explicitly name or contrast with siblings.

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?

It provides context that the node is inserted under an existing parent, but it offers no explicit when-to-use guidance versus alternatives such as add_nodes, move_node, or patch_site_node, and no when-not conditions.

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