nodes_delete_node

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

With no annotations provided, the description carries the full behavioral burden and falls well short: it does not state that deletion is irreversible, what happens to users/connections bound to the node, or whether authorization is required. The only behavioral detail (the confirm preview flow) lives in the schema's confirm parameter, not in the description.

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?

It is short and front-loaded, but two of its three lines (the raw endpoint and the Tags line) are boilerplate that restate the tool name or add nothing. It is under-specified rather than efficiently concise.

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 no annotations, no output schema, and half its parameters undocumented, the description omits critical context: irreversibility, cascade effects on attached users, and the required confirm:true handshake that governs whether the call even executes.

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 50%: uuid has no description anywhere, and confirm's description is schema-side only. The description text adds no meaning about either parameter, so it fails to compensate for the coverage gap.

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 states a specific verb and resource ('Delete a node') and even exposes the underlying HTTP method and path, so an agent knows exactly what operation this is. It does not differentiate from adjacent siblings such as nodes_disable_node or nodes_bulk_nodes_actions, which is the one gap keeping it from 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?

There is no guidance on when to use this instead of alternatives (disable vs delete vs bulk delete), nor any stated prerequisites such as whether the node must be disabled or drained first. The 'Tags: Nodes Controller' line is metadata, not usage guidance.

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