delete-template

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

Discloses that the operation is destructive, permanent, and requires user confirmation, plus suggests verifying the id with list-templates. Lacks details on error handling or side effects, but sufficient for a simple delete.

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?

Four concise sentences covering usage, returns, alternatives, and safety. No redundant information.

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?

Given the simplicity of the tool (one parameter, delete operation), the description covers all necessary aspects: purpose, guidelines, return value, and safety. Output schema likely confirms the return structure.

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?

The single 'id' parameter is explained as the template identifier, but no format or source details are given. With 0% schema coverage, the description partially compensates by referencing list-templates to confirm the id.

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 clearly states the tool deletes a saved email template permanently by id, and distinguishes from get-template (view) and save-template (update) in the usage guidelines.

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?

Explicitly states when to use (permanently removing a template by id) and when not to use (viewing or updating), with specific alternative tool names.

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