delete_whatsapp_template

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

Description adds value beyond annotations by explicitly marking the tool as destructive and advising user confirmation. It includes the HTTP method and URL, which clarify the operation. However, it repeats the purpose without additional behavioral details.

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 repetitive ('Delete WhatsApp Template' appears three times) and includes a URL that may not be necessary. It could be condensed into a single sentence without loss of clarity.

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 good annotations, the description provides essential safety warnings but lacks details on return values or side effects. It is functionally adequate but could be more complete.

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 only states 'Deletes a WhatsApp Template by Id.' without elaborating on the 'id' parameter, its format, or constraints. This fails to compensate for the lack of schema documentation.

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 'Delete WhatsApp Template' and uses the verb 'delete' with a specific resource. It distinguishes itself from sibling delete tools by targeting WhatsApp templates specifically.

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?

No guidance on when to use this tool vs alternatives like other delete tools or update operations. The name implies usage for WhatsApp templates, but no explicit context or exclusions are provided.

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