WhatsApp Business MCP

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

With no annotations provided, the description carries the full burden of disclosure. It successfully communicates the destructive nature ('permanently deletes') and the broad scope ('ALL language variants'). It also notes the return type ('JSON confirming deletion'), though given the output schema exists, this is adequate confirmation.

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 appropriately sized with a clear structure: action statement, critical warning, parameter definition, and return type. Every section earns its place, particularly the warning which is front-loaded. The Args/Returns format is slightly formal but efficient for a single-parameter tool.

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 the tool's simplicity (1 parameter, nested objects=false) and the presence of an output schema, the description is complete. It covers the essential behavioral warning about language variants that the schema cannot express, and acknowledges the return format without needing to detail the JSON structure.

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?

The schema has 0% description coverage (only a title). The Args section compensates by stating 'Name of the template to delete,' which clarifies the parameter's purpose beyond the schema's type information. This successfully bridges the documentation gap for the single required parameter.

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 opens with 'Delete a WhatsApp template by name,' providing a specific verb (Delete), resource (WhatsApp template), and scope (by name). The warning about deleting 'ALL language variants' further distinguishes this tool's scope from potential siblings that might handle single-language deletion.

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 WARNING section provides critical context about the irreversible scope (permanent deletion of all language variants), which guides the agent on the gravity of the operation. However, it lacks explicit guidance on when to use this vs. alternatives like update_template, or prerequisites like checking template status first.

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