delete_template

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

No annotations provided, but the description thoroughly covers behavioral aspects: marks the operation as irreversible, mentions authentication via API key, max 10 concurrent requests, support for read-only and dry-run modes, and specific error response (404) for invalid template_id.

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 well-structured with clear sections (Args, Returns) and bullet points. It is detailed but not excessively long for the information conveyed. Minor verbosity could be trimmed, but overall efficient.

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 that an output schema exists and the description also specifies the return format (JSON with status and template_id), the tool definition is complete. It covers prerequisites, error conditions, concurrency limits, and behavioral notes.

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 0%, but the description adds significant value by explaining the template_id parameter: it is a numeric string (e.g., '12345') and must be of type 'user'. This goes beyond the schema's bare type definition.

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 user-created template permanently, specifying it only applies to user-created templates, not gallery or base templates. It differentiates from list_templates, which is used to find template IDs.

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 (only user-created templates) and when not to use (gallery and base templates cannot be deleted). Provides alternative tool (list_templates) and warns that campaigns already using template content are unaffected.

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