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 covered structurally; the description adds nothing on top — no statement about permanence, whether templates in use can be deleted, or what happens to linked automations/messages. No contradiction, but zero added context for a destructive operation.

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?

It is a single short sentence with no waste, but this is under-specification rather than conciseness — the entire description could be deleted without losing information, since it merely echoes the title.

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, non-readonly tool with no output schema, the description should convey consequences (hard vs soft delete, cascading effects) and any preconditions. Annotations cover the safety flags, but an agent still cannot predict the effect of calling 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 description coverage is 100% and the single `id` parameter is documented as 'Template id' in the schema, so the baseline of 3 applies. The description adds no format hints (e.g., where to obtain the id) beyond what the schema provides.

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 restates the tool name and title ('Delete a template') without adding scope, and it does not distinguish this from the many sibling delete_* tools (delete_segment, delete_list, delete_webhook, etc.). An agent learns nothing beyond the verb+resource already encoded in the name.

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?

No guidance on when to use this versus update_template, get_template, or list_templates, and no prerequisites or exclusions stated. The agent must infer entirely from the name that this is the removal path for templates.

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