delete_multiple_nodes

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'delete', which is inherently destructive, but gives no details about reversibility, partial failures, error handling, permissions, or whether deletion is atomic. This is a minimal disclosure that adds little beyond the tool's name and schema.

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 redundant words. Every word earns its place, and the message is immediately clear.

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 simple tool with one parameter and no output schema, the description is adequate but not complete. It covers the core action but omits important context like what happens when a node ID is invalid, whether the operation is atomic, or whether there is any confirmation. Given the lack of annotations and output schema, more detail would help.

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 baseline is 3. The description does not add any extra meaning to the nodeIds parameter beyond what the schema already provides. It names the parameter but provides no additional context about ID formats or expected values.

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 a specific action (delete) on a specific resource (nodes from Figma), with the scoping word 'multiple' distinguishing it from the sibling delete_node tool. It is immediately obvious what the tool does and how it differs from the singular delete variant.

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 usage: use when you need to delete multiple nodes in one call. However, it does not explicitly state when NOT to use it, nor does it mention the alternative delete_node for single deletions. The guidance is inferred from the name and wording rather than explicitly spelled out.

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