delete_template

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

Beyond the destructiveHint annotation, the description discloses that deletion is irreversible and that a confirmation flag is conditionally required. This tells the agent that the operation is permanent and may require extra steps depending on the environment, which is valuable behavioral 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 compact, using two short sentences. The core action is front-loaded, followed by the most important caveat (irreversibility) and the conditional confirmation requirement. No words are wasted.

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 two-parameter delete tool with destructiveHint already annotated, the description covers the essential operational details: what is deleted, that it is irreversible, and when confirmation is required. No critical information is missing for an agent to invoke it correctly.

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 coverage is 100%, and both 'id' and 'confirmed' are already described in the input schema. The description reinforces the confirmed parameter's role and ties it to the environment flag, but it does not add substantial semantics beyond what the schema already documents.

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 a specific action ('Delete') on a specific resource ('saved email template'), making the tool's purpose immediately clear. It also distinguishes this from sibling deletion tools like delete_email and delete_draft by explicitly limiting the scope to templates.

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 clear context for when this tool is appropriate: deleting a saved email template. It also gives invocation guidance by noting the irreversible nature and the confirmed:true requirement under PROTONMAIL_CONFIRM_DESTRUCTIVE. It does not explicitly compare against alternatives, but the resource-specific wording makes the intended use clear.

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