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. It discloses the Meta approval domain and enumerates possible status values (APPROVED, PENDING, REJECTED), but omits operational details like rate limits, authentication requirements, or error behaviors when templates are not found.

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?

Excellent structure with clear sections (purpose, usage guidance, Args, Returns). Front-loaded with the core function, zero redundant text, and appropriate use of docstring-style formatting to organize parameter and return value documentation.

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?

Appropriate for the tool's complexity (2 optional parameters, simple scalar inputs). The Returns section adequately describes the output semantics given that a formal output schema exists. Could be improved by noting error conditions or parameter validation rules.

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?

Despite 0% schema description coverage, the Args section adds crucial semantic context: template_id is explicitly identified as 'Meta template ID' (distinguishing it from internal IDs) and 'directly' implies it's the canonical identifier. However, it fails to clarify the parameter relationship (mutually exclusive vs. hierarchical) or that both are optional.

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 states a specific verb ('Check') and resource ('approval status of a WhatsApp template'), clearly distinguishing it from sibling tools like create_template or send_template_message which perform actions rather than status monitoring.

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 explicit temporal guidance ('Use this after creating a template') establishing the workflow sequence, and clarifies the specific value proposition ('see if Meta approved or rejected it'). Lacks explicit 'when not to use' guidance contrasting with get_template_detail.

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