delete_whatsapp_template

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

With no annotations, the description fully bears the behavioral disclosure burden. It reveals that deletion is a mutation requiring confirmation, describes the special response flow, and marks it as a dangerous action. It does not discuss side effects or permissions, but the main behavior is well explained.

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 paragraph, front-loaded with purpose, then details the confirmation flow. While it could be slightly more concise, every sentence serves a purpose and the flow explanation is crucial for correct usage.

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 description covers the confirmation behavior, which is critical for this tool. There is no output schema, but the description explains the expected response format (requires_confirmation=true, success=false). It lacks details about success after confirmation, but given the deletion nature and lack of output schema, it is sufficient.

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?

Input schema already describes both parameters (id and confirm). The description adds value by explaining the confirm parameter's role in the confirmation flow and the need to pass true for execution, extending beyond the schema's basic description.

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 'Eliminar plantilla de WhatsApp' and 'Elimina una plantilla de mensaje de WhatsApp', specifying the verb (delete) and resource (WhatsApp template). This distinguishes it from sibling tools like delete_contact_list or delete_agent.

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 explicit guidance on the confirmation flow: it explains that the action will return requires_confirmation=true with success=false, instructs the agent to describe to user and stop, and notes not to call again. It also states that confirm=true is required to execute, which is excellent usage guidance.

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