delete_template

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

No annotations are provided, so the description carries the full burden, yet it says nothing about this being an irreversible destructive mutation, whether deletion of a template in use is allowed, or what errors/permissions apply. A one-word restatement leaves the agent blind on 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 short, but its brevity comes from omission rather than efficiency; it is under-specified for a destructive mutation. Nothing is front-loaded because there is nothing to front-load.

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, no-annotation, no-output-schema tool surrounded by CRUD siblings, the description omits confirmation semantics, irreversibility, and failure conditions. It is not sufficient for an agent to invoke it safely.

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 required param 'id' is documented as 'Template UUID' in the schema. The description adds nothing beyond that, which meets the baseline 3 when the schema already does the work.

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 'Delete a template.' merely restates the tool name and title; it adds no verb detail, scope, or resource qualification beyond what the identifier already conveys. It is a tautology rather than a specification of what is deleted or by which identifier.

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 indication of when to use this versus get_template, update_template, or list_templates, and no prerequisites (e.g., confirming template is unreferenced). The agent must infer everything from the name alone.

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