Remove Node

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

With no annotations, the description explains the side effect of removing connected edges but does not disclose whether the operation is reversible, permissions required, or behavior on invalid input.

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, front-loaded with core purpose and a concise conditional. No redundant information.

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 tool with one optional parameter, the description covers the main action and edge effects. Lacks details on error handling or prerequisites but is generally sufficient.

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 description adds meaning beyond the schema by explaining that nodeId is optional and defaults to the selected node, which is critical semantic information given 0% schema description coverage.

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 tool removes a canvas node and its connected edges, with a specific fallback behavior when nodeId is omitted. This distinguishes it from siblings like connect_nodes or disconnect_nodes.

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?

The description implies when to use (when you want to remove a node and its edges) and provides a condition for omitting nodeId, but does not explicitly state when not to use this tool or mention alternatives like disconnect_nodes.

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