Delete Template

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so safety is covered structurally. The description adds genuinely new behavioral context: that explicit confirmation is mandatory for this exact action, that provider charges/hosting/sharing consequences may apply, and that unknown outcomes must not be auto-resubmitted (consistent with non-idempotency). This goes beyond the annotations without contradicting them.

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 action statement is front-loaded, which is good, but the raw HTML base-URL anchor is markup clutter that conveys little to an agent and the 'unknown outcomes' sentence is generic boilerplate. The core payload is two short sentences, so it is not bloated, just partially padded.

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 delete with full annotation coverage, a fully documented 3-parameter schema, and no output schema to explain, the description supplies the two things the structured fields cannot: the mandatory confirmation semantics and the charge/resubmission warnings. Nothing critical is missing for correct invocation.

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%, so all three parameters (id, account, confirm) are already documented in the schema itself, and the baseline of 3 applies. The description restates that deletion targets a template id but adds no syntax, format, or account-selection detail 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 opening sentence names a specific verb and resource ('Delete a template by its template id'), which is unambiguous and clearly separable from the other delete_* siblings (delete_asset, delete_source). It does not explicitly state what differentiates it from those siblings beyond the resource noun, so it stops short of a 5.

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 gives a real precondition ('Explicit confirmation is required for this exact action') and a recovery caveat ('Never automatically resubmit unknown outcomes'), which is useful operational guidance. However, it never contrasts this tool with alternatives such as update_template or delete_asset, and does not state when deletion is appropriate versus archiving, so usage is only implied.

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