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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description earns credit for adding genuine context beyond them: it discloses the blast radius, namely that emails already generated from the template retain their own copy and are not affected. It still says nothing about whether the call fails when the template is used by an in-flight campaign, or about permissions.

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?

Two short sentences, zero waste, with the action stated first and the non-obvious side-effect qualification immediately after. Nothing is padded or repeated from the name.

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 one-parameter destructive tool with full annotation coverage of the safety profile and no output schema, the definition covers what an agent needs to call it and what the consequence is. The remaining gaps, permission requirements and behavior on in-use templates, are minor rather than blocking.

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 0%, but the sole parameter template_id is a self-evident string identifier with no format ambiguity. The description adds no meaning to it, and there is little to add; a baseline 3 fits a single obvious parameter.

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 and resource ('Delete a template') that an agent can map directly onto the delete_template name and distinguish from get_template/update_template. It does not, however, differentiate itself from the many other delete_* siblings beyond the resource noun.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as update_template or list_templates. The agent must infer that this is the permanent-removal path from the verb alone.

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