delete_template

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

The description labels the tool as 'Destructive' and mentions 'permanently delete', but with no annotations, more detail on consequences (e.g., impact on associated campaigns, irreversibility) would improve transparency. The description adds minimal value over the schema's parameter description.

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 a single sentence, which is concise. However, it barely covers necessary information; breaking into two sentences could improve readability without adding length.

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 simple destructive tool with two parameters and no output schema, the description covers the essential points: action, resource, and required confirmation. However, mentioning that the action is irreversible or where to find the template_id could enhance completeness.

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%, so baseline is 3. The description does not add new meaning; it restates that confirm_delete must be true and implies template_id is the identifier. No extra syntax or format details are provided.

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 verb 'delete' and the resource 'dynamic template', and specifies the tool is for permanent deletion. It distinguishes from siblings like delete_template_version.

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 includes the requirement 'confirm_delete: true', which is a usage guideline, but lacks explicit guidance on when to use this tool versus alternatives (e.g., deactivating a template or deleting a version). No when-not-to-use or alternative suggestions are provided.

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