Delete a template version

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

Annotations already mark destructiveHint and idempotentHint. The description adds a critical behavioral constraint (cannot delete published version), which goes beyond the annotations. No contradiction with annotations.

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 very short (one sentence, 8 words) and front-loads the action. It is concise, though it could optionally include more context without becoming verbose.

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?

Lacking: no output schema, no mention of success response (e.g., 204 No Content), prerequisites (e.g., template must exist), or potential side effects. The single constraint is useful but incomplete for a deletion operation.

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 input schema already provides pattern and description for both parameters (template_id and version_id) with 100% coverage. The description does not add any additional meaning or examples beyond what the schema specifies.

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 action ('Delete') and the resource ('a template version'), and adds a specific constraint ('Cannot delete the currently published version') that distinguishes this tool from other deletion tools like lob_templates_delete, which operate on templates rather than versions.

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 a negative usage guideline (not to delete the published version) but does not explicitly state when to use this tool or offer alternatives like lob_templates_delete for full template deletion or lob_template_versions_update for modifications.

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