delete_node

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Delete a node' and does not disclose side effects such as irreversibility, cascading deletion of children, connection impacts, or error behavior on invalid paths. This is a significant gap for a mutation/destructive tool.

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 extremely short and front-loaded, with no filler, but it also includes an 'ctx: MCP context' argument that does not appear in the input schema. This is slightly confusing and reduces the efficiency of the structure.

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 single-parameter operation with no annotations and no output schema, the description is too sparse. An agent is not told what happens after deletion, whether the action is undoable, how to reference nodes reliably, or what errors might arise. More context is needed for safe and correct invocation.

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 0%, and the description merely restates 'node_path: Node path,' which repeats the schema property name/title without adding format guidance, examples, or path syntax. With no schema descriptions, the description should compensate but does not.

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.' This clearly distinguishes it from sibling node helpers like create_node, rename_node, copy_node, and move_node. Even without an explicit target context, node deletion is unambiguous.

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 guidance is given about when to use this tool versus alternatives, or about preconditions/cautions. Given it is a destructive operation, the description should at least warn about irreversibility or mention that it is intended for removing existing nodes from the network, rather than other node operations.

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