map_delete_node

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does reveal the important side effect that connections are deleted along with the node, which is valuable. However, it does not mention irreversibility, permissions, or error behavior, leaving potential gaps for a destructive operation.

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, clear sentence that front-loads the action and its consequence. No wasted words, perfectly sized for the tool's simplicity.

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?

The tool is simple (one param, no output schema) and the description covers the primary behavior and a key side effect. It is complete enough for an AI agent to understand the tool's likely effect. Minor details like what happens if the node does not exist are not necessary for basic 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?

The schema provides 100% coverage for the single parameter 'id' with description 'Node id'. The tool description also mentions 'node', reinforcing the context. Since schema coverage is high, the description does not need to add much; it meets the baseline with no additional detail.

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 ('delete'), identifies the resource ('a node'), and states the scope ('and all its connections'). This clearly distinguishes it from sibling tools like map_delete_connection and map_delete_sticky.

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 the tool (when you want to remove a node), but it does not explicitly mention alternatives, prerequisites, or exclusions. No guidance is given on when to choose this over map_delete_connection or map_delete_sticky, but the name and description are self-explanatory.

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