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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered structurally. The description adds a useful ownership constraint ('belonging to your team'), but says nothing about irreversibility, whether deletion is permanent or reversible, or what happens if the template is referenced elsewhere.

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 front-loaded sentence with zero filler. The verb, resource, and scope are all established immediately.

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, the description plus annotations convey the core action and safety profile. However, it omits prerequisites (where template_id comes from) and the consequences of deletion, which matter for an irreversible operation.

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?

There is a single required parameter, template_id, with 0% schema description coverage and no type hint in the description. The description never explains what the id refers to or how to obtain it (e.g., via list_templates), leaving all parameter semantics to the bare schema.

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 pairs a specific verb ('Delete') with a specific resource ('writing template') and adds an ownership scope ('belonging to your team'). It clearly distinguishes itself from create_template, update_template, and list_templates in the sibling set without needing to name them.

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 guidance on when to use this versus update_template or archive-like alternatives, and no stated precondition such as fetching the template_id from list_templates first. The deletion intent is implied by the verb, but nothing is spelled out.

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