send_whatsapp_message

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates the tool is a write operation (POST) and requires authentication, but does not disclose potential side effects, rate limits, or error scenarios. The batch nature is mentioned, which adds some transparency.

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 concise, consisting of one sentence plus a requirement note. It front-loades the endpoint and key function. However, it could be more structured by separating the requirement into a dedicated line or bullet.

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 complexity (nested objects, multiple parameters) and absence of an output schema, the description fails to explain what the tool returns or how to interpret the response. Users of sibling status tools may infer the behavior, but the description itself is incomplete.

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 75%, meaning most parameters have descriptions in the schema. The tool description adds little beyond stating 'batch' and the endpoint. No additional constraints, examples, or explanations are provided for parameters like headers or placeholders.

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 the tool sends batch WhatsApp template messages via a specific POST endpoint. It explicitly uses 'batch' and 'template messages' which distinguishes it from sibling tools like send_sms, and the mention of the endpoint URL adds specificity.

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 mentions the requirement for 'X-API-VASKEY' but provides no explicit guidance on when to use this tool vs alternatives such as whatsapp_message_status or get_whatsapp_templates. Usage context is implied by the resource name, but no exclusions or conditions are specified.

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