WhatsApp Business MCP

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

No annotations are provided, so the description carries the full disclosure burden. It successfully explains the asynchronous approval process ('go through Meta's review process') and return value structure. It could improve by mentioning idempotency concerns (duplicate names) or error behavior specifics.

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?

Well-structured with clear sections (purpose, Args, Returns). The length is justified given the complexity of the components parameter. Information is front-loaded with the core action in the first sentence, and the extensive example is essential for the nested component structure.

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 high complexity of WhatsApp template components and the presence of an output schema (which the description briefly summarizes without redundancy), the description provides complete contextual coverage. The detailed Args example is critical for correct invocation given the lack of schema documentation.

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?

With 0% schema description coverage, the description fully compensates by providing detailed constraints for each parameter: name formatting rules (lowercase, underscores, max 512), category enums (MARKETING/UTILITY), language format examples, and a comprehensive JSON example for the complex components structure.

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 a precise action ('Create and submit') and target resource ('WhatsApp template to Meta for approval'). It clearly distinguishes this from sibling tools by explicitly mentioning check_template_status as the follow-up action for monitoring the approval process.

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?

Provides clear workflow context by stating templates go through Meta's review process and directing users to check_template_status afterward. However, it does not explicitly contrast with validate_template (when to validate vs. create) or clarify failure/retry scenarios.

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