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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is mostly carried by structured data. The word 'Permanently' adds a small amount of value by signaling irreversibility, but the description says nothing about what is destroyed beyond the template record, whether deletion fails if the template is in use, or any auth/scope requirement.

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?

One short sentence with the action front-loaded and no filler. It is efficiently sized, though the terseness leaves room that could have been used for a caveat about irreversibility or in-use templates.

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 single-parameter mutation, the annotations already carry the risk profile and the schema fully documents the input, so nothing critical is missing for a correct call. However, no output schema exists and the description gives no hint of the response or failure modes, leaving it only minimally viable.

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 the single parameter 'id' is documented in the schema as 'Template ID (tem_xxx)', so the description has no gap to fill. The baseline of 3 applies: the schema does the work, and the description adds nothing about the identifier.

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 (delete) and resource (template), clearly distinct from sibling delete-* tools that target other resources. It does not explicitly distinguish from unpublish-template or update-template, but the action is unambiguous.

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 guidance on when to use this versus alternatives such as unpublish-template (which likely removes a template from availability without destroying it) or update-template. No preconditions, no mention of what happens when a template is still referenced by emails or campaigns.

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