remove_geometry_node

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

The description explicitly mentions 'delete', indicating a destructive operation. However, it does not mention any side effects, irreversibility, or conditions for the removal.

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 extremely concise, consisting of a single short sentence. It is to the point with no unnecessary words.

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?

While the action is clear, the lack of parameter explanation and any contextual details makes it incomplete for an agent that needs to correctly invoke the tool. The agent would have to infer meaning from the tool name and sibling context.

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 gives no explanation of the 'node' and 'node_group' parameters. The schema also lacks descriptions, so the agent receives no help in understanding what values to provide.

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 states the exact action (delete) and the resource (geometry node), which clearly distinguishes it from sibling tools like add_geometry_node or build_geometry_node_tree.

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. The description only states the action, with no context on typical scenarios or prerequisites.

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