delete_node

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

The description is terse and provides no behavioral details beyond the word 'delete'. Since no annotations are present, the description carries the full burden of disclosing that this is a destructive, likely irreversible operation that may also delete child nodes. No such context is provided.

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, front-loaded sentence with no wasted words. It immediately conveys the core action and resource, making it an appropriately sized and concise description for a simple tool.

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?

Given the tool's simplicity (one parameter, no output schema), the description is minimally viable. However, it lacks any mention of the destructive and permanent nature of the operation, which is arguably essential context for a delete tool. It is adequate but has clear gaps in behavioral disclosure.

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 already provides full coverage for the single parameter 'nodeId' with a clear description. The tool description adds no additional parameter semantics, so it earns the baseline score of 3 without enhancing or reducing understanding.

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 action ('delete') and the resource ('a node'), and it specifically targets a single node, which distinguishes it from the sibling tool 'delete_multiple_nodes' by implication. However, it doesn't explicitly name the sibling or clarify the single-vs-multiple distinction, so it stops slightly short of full distinction.

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 provided on when to use this tool versus alternatives like 'delete_multiple_nodes'. The description is purely definitional and does not offer any context about appropriate scenarios, prerequisites, or exclusions.

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