Delete a caption template

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds that user confirmation happens first, which is useful context above the annotations. However, it does not say whether deletion is permanent or recoverable, nor what happens if the name is not found.

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?

Two short sentences, action first, caveat second. Every word is doing work and nothing is redundant, which is exactly right for a two-parameter destructive tool.

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 tool with no output schema, the definition covers the essential action and the confirmation requirement, and the schema documents the token flow. It stops short of describing failure behavior, irreversibility, or the meaning of the required name parameter, which an agent would need for confident 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 coverage is 50%: confirmation_token is well documented in the schema, but the required 'name' parameter has no description in either place. The description's word 'file' hints that name may be a filename, yet it never clarifies whether it is a template name, slug, or path, and it does not explain the round-trip of re-calling with identical arguments. Baseline 3 is appropriate given partial schema coverage.

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 states a specific verb and resource: 'Deletes a saved template file.' This is clearly distinguishable from the sibling tools list_templates and save_template, though it does not name those siblings explicitly. The agent can tell what the tool does without needing to consult the schema.

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?

'Asks the user first' implies a two-step confirmation flow, which is the closest thing to usage guidance here. It does not say when to choose deletion versus, for example, overwriting a template via save_template, nor does it state prerequisites such as the template having to exist.

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