Delete Template

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds valuable context: it is a soft delete (marked for garbage collection), default delay of 24 hours, and the ability to use update_template_metadata for immediate deletion. This goes beyond annotations but could provide more detail on the garbage collection process.

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 description is concise with only three sentences. The primary action is stated first, followed by key behavioral details and an alternative. No unnecessary words, well-structured.

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 one parameter and no output schema, the description covers the core behavior (soft delete, two ID types) and provides an alternative tool. It is complete enough for an agent to select and use the tool correctly, though it could mention return behavior or error handling.

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 schema already has a detailed description of the templateId parameter (64-bit or SHA-256, effects of each type). The description adds the context of soft delete but does not introduce new parameter semantics beyond what the schema provides. With 100% schema coverage, the description does not need to repeat, but also does not add extra clarity.

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 primary action ('Delete a stored Carbone template') and specifies it is a soft delete. It distinguishes between deleting by Template ID (all versions) and Version ID (specific version), and contrasts with the sibling tool update_template_metadata for immediate deletion.

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 provides explicit guidance on when to use this tool versus alternatives, including when to use update_template_metadata for immediate or scheduled deletion. It also explains the two deletion modes (by Template ID or Version ID), helping the agent choose correctly.

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