figma_delete_node

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

No annotations are provided, so the description carries the full burden. It discloses batch capability ('one or more') but does not mention that deletion is likely permanent, does not discuss impact on child nodes, undo behavior, or any permissions needed. The description is minimal and lacks safety context.

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 short, unambiguous sentence with no filler or redundancy. It earns its place by stating the core purpose effectively.

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 that there are no annotations, no output schema, and only two simple parameters, the description is under-specified. It does not mention the destructive nature, return value, or any side effects. For a mutation tool, this is a notable gap.

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 the meaning that the operation supports one or more nodes, implying that nodeId is for a single node and nodeIds for multiple. However, it does not clarify the exact relationship between the two parameters, whether they are mutually exclusive, or if at least one is required. Schema coverage is 0%, so the description partially compensates but remains vague.

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 ('nodes'), and explicitly notes that it supports 'one or more', which distinguishes it from single-node deletion tools. The verb is specific and the resource is unambiguous, making the purpose immediately clear.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, whether it affects the current file or selection, or any exclusion criteria. There is no comparison with sibling tools like rename_node or move_node.

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