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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds non-obvious behavior beyond that: the deletion is cascading ('and its subtree') and four protected sentinel nodes are rejected. It doesn't mention permission requirements or irreversibility, but the cascade and protected-node rules are meaningful additions.

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, zero filler, and the core action is front-loaded ahead of the constraint. Every clause earns its place.

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 destructive mutation with a fully documented schema and annotations carrying the safety hints, the description covers the two things an agent most needs: that it cascades and which nodes are protected. No output schema exists, so nothing about returns is owed, but permission/auth prerequisites are left unstated.

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 100%, and the schema already documents both id and nodeId, including the source hint (list_site_nodes / search_site_nodes). The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 (Delete) and resource (node) plus the important scope detail that the entire subtree goes with it. The resource 'node' is distinct from sibling delete operations (delete_page, delete_site, delete_collection), so an agent can route correctly.

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?

Provides explicit exclusions — ROOT, page_home, hdr_root and ftr_root cannot be deleted — which is real when-not guidance. It stops short of stating when to prefer this over siblings like delete_page or move_node, so it is clear context without full alternative routing.

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