Delete Node

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

There are no annotations to disclose safety or side effects, so the description must carry the burden. It only states 'Remove a node,' implying a destructive action, but does not mention irreversibility, what happens to child nodes, connections, or undo behavior. This is significant behavioral information absent from 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?

The description is a single, focused sentence with no unnecessary words or filler. It is appropriately sized for the tool's simple purpose.

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 simple delete operation with one parameter and no output schema, the description is minimally adequate but lacks important contextual details such as error behavior, whether the node must exist, or side effects on related nodes. It does not mention if the operation is reversible or what the expected result is.

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?

The input schema has 100% description coverage for the single parameter (nodeId: 'Node ID to delete'), so the schema already explains the parameter fully. The description adds no additional parameter semantics beyond the schema, but this is acceptable given the high coverage and simple parameter.

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 uses a specific verb ('Remove') and a specific resource ('a node from the canvas'), making the tool's function immediately clear. It also distinguishes itself from sibling tools like ungroup_node, reparent_node, and clone_node by clearly indicating deletion rather than structural changes or duplication.

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 instead of alternatives. For example, there is no mention of whether to use batch_operations for multiple deletions, or whether ungroup_node should be considered first. The description provides no context about prerequisites or exclusions.

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