delete_node

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

The description adds context beyond the destructiveHint annotation by noting automatic saving, inability to delete the root, and the return format. It also mentions that all children are removed. While it doesn't discuss reversibility or undo, the level of detail is appropriate for a deletion 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 two sentences with no wasted words. The first sentence clearly states the primary action, and the second covers usage guidance, constraints, and return value. It is front-loaded and efficiently packed with 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 deletion tool with no output schema, the description is complete: it covers the action, scope (including children), auto-save behavior, constraints (cannot delete root), error condition, and the return format. No additional information seems necessary for an agent to use the tool correctly.

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 100%, so the parameters are already well-documented in the schema. The description does not add significant new information about parameter formats or usage beyond what the schema provides, earning a baseline score of 3.

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 starts with 'Remove a node and all its children from a Godot scene file,' which is a specific verb+resource. It distinguishes from sibling tools like add_node by stating 'for replacing a node in place, pair with add_node.' This makes it clear and differentiates it from similar operations.

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?

Explicitly states 'Use when pruning the scene tree' and provides an alternative approach: 'for replacing a node in place, pair with add_node.' Also clarifies constraints: 'Cannot delete the scene root' and error conditions: 'Errors if nodePath does not exist.' This gives the agent clear context for when and how to use the tool.

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