delete_multiple_nodes

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only restates the name ('Delete multiple nodes at once') and adds the minor detail that the operation is a batch. It does not mention that deletion is destructive and potentially irreversible, how invalid node IDs are handled, or any side effects.

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 sentence, immediately front-loaded with the verb 'Delete', and contains zero filler words. Every word contributes to conveying the core purpose.

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 destructive tool with no annotations and simple schema, the description is too thin to be fully contextually complete. It omits critical warnings about the irreversible nature of deletion and any necessary caveats, such as how nested or child nodes are handled or whether confirmation is required.

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 schema already provides a clear description for the only parameter ('nodeIds' = 'Array of node IDs to delete'), achieving 100% coverage. The tool description adds no extra information about parameter format, constraints, or error cases, so the baseline score of 3 is appropriate.

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'), the resource ('multiple nodes from Figma'), and the batch nature ('at once'). It effectively distinguishes from the sibling tool 'delete_node' by explicitly indicating multiple nodes.

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 does not provide any guidance on when to use this tool versus alternatives like 'delete_node'. It does not mention prerequisites, batch limits, or situations where single deletion is preferred, leaving usage to be implied solely by the tool name.

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