delete_template

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

No annotations provided; description fully covers behavioral traits: irriversibility, authentication, rate limits (max 10 concurrent), read-only/dry-run respect, and error conditions (404). This exceeds the burden for an unannotated tool.

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?

Well-structured with clear paragraphs and bullet points. Every sentence adds value: action, constraints, alternatives, parameters, returns. No fluff, highly readable.

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?

Tool has single parameter, no enums, and output schema. Description covers all necessary context: prerequisites (list_templates), return format, error handling, side effects, and usage boundaries. Fully complete for this tool's complexity.

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?

Single parameter template_id receives detailed meaning: numeric string example and requirement to be of type 'user'. Schema only shows type string; description adds crucial context beyond the 0% schema description coverage.

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?

Description clearly states 'Delete a user-created template permanently.' It specifies verb (delete), resource (user-created template), and distinguishes from gallery/base templates and sibling tools like create_template and update_template.

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 (user-created templates), when not (gallery and base templates), and directs to list_templates for finding IDs. Also clarifies no effect on existing campaigns, providing comprehensive usage guidance.

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