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

Annotations already flag destructiveHint=true and idempotentHint=true, so safety is largely covered. The description adds genuinely new behavioral context that annotations cannot express: already-sent signature requests are unaffected, i.e. the delete is non-cascading. It does not state irreversibility or error behavior for an invalid ID, keeping it short of a 5.

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?

Three short sentences, destructive action front-loaded, with no filler. "Confirm with the user first" borders on restating the destructiveHint annotation, but it is short and actionable enough to earn its place.

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 single-parameter delete with no output schema, the description covers the essential agent-facing facts: it destroys something, it is non-cascading, and confirmation is expected. Only the identity/format of template_id and failure behavior are left unaddressed.

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 0% and there is one parameter, template_id, which the description never mentions. The name is fairly self-explanatory, but the description supplies no format, source, or constraint information to compensate for the empty 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 gives a specific verb and resource ("Delete a saved template"), which cleanly separates it from sibling reads and mutations like get_template, list_templates, and update_template. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated.

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?

"Confirm with the user first" is a useful operational guideline, but it says nothing about when to delete versus archive/update, or what preconditions must hold. Usage is implied by the destructive verb rather than spelled out against alternatives.

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