wa_delete_template

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

With no annotations, the description carries the full burden of behavioral disclosure. It lacks any detail about the destructive nature beyond the word 'delete', implications for sent messages, permission requirements, or the effect of the 'confirm' parameter. This is a significant gap for a mutation 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?

The description is a single concise sentence, making it easy to parse. However, it is terse to the point of under-specification, lacking essential context that should accompany deletion tools. Still, given the low information content, it is not 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?

The tool has 3 parameters, no output schema, and no annotations. The description fails to explain the deletion process, the purpose of the confirm flag, or any constraints (e.g., template must exist, cannot be deleted if in use). This is far from complete for a potentially dangerous 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?

Schema description coverage is 0%, and the description does not compensate. Only 'template_name' is implicitly mentioned via 'by name'; 'waba_id' and especially 'confirm' are completely unexplained. The description adds no value beyond the schema field names.

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 (template), and specifies the key attribute (by name). It distinguishes from sibling tools like wa_create_template and wa_list_templates by being the delete operation, though it doesn't explicitly mention scoping to a WABA.

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 no guidance on when to use this tool versus alternatives, ideal scenarios, or prerequisites. Although the tool name clearly indicates deletion, there is no explicit context about when deletion is appropriate (e.g., only for unused templates) or any mention of the confirm parameter's role.

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