Bulk delete templates

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real behavior: all-or-nothing atomicity (none deleted if any template is referenced), a version prerequisite (Plunk v0.12+), the 1000-item cap, and a confirmation prompt. These are exactly the traits an agent needs before invoking a destructive batch operation and are not derivable from the annotations.

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 labeled sections (Purpose / Not for / Returns / Use when / Note) front-load the critical routing and safety information, and every line is short. 'Returns: The outcome of the batch' is thin filler, but it costs almost nothing.

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 single-parameter, non-nested tool with no output schema, the description covers purpose, alternative, preconditions, destructive semantics, and failure mode. Nothing an agent needs to invoke it correctly is missing.

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% and there is a single 'ids' parameter, so the schema already documents the UUID format, maxItems 1000, and the referenced-template failure condition. The description restates the cap and the failure mode but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (permanently delete), resource (templates), and scope (up to 1000 in one atomic call). It also explicitly names the sibling it is not for (plunk_delete_template), so an agent can route between the two without opening either schema.

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?

Provides explicit when-to-use ('clearing out many templates at once, typically after an audit') and an explicit when-not-to-use with the alternative named ('Not for: A single template — plunk_delete_template is clearer'). Nothing is left to inference.

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