send_a_whatsapp_template_message

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds that messages are irreversible once delivered, which is useful behavioral context beyond annotations. However, it does not disclose auth requirements, rate limits, or what happens on failure. The behavioral transparency is adequate but not rich.

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, with key information front-loaded in the structured header line. The explanation is direct and avoids verbosity. Minor repetition (e.g., 'Send a WhatsApp Template' appears twice) but overall efficient.

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?

No output schema is provided, and the description does not explain the return value or error responses. It mentions scheduling but does not detail how to schedule. For a 2-parameter tool with nested objects, the description covers the core usage but misses some contextual details like prerequisites (e.g., template must exist) and scheduling mechanics.

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 coverage is 100%, so parameters are well-documented. The description restates the need for a template ID, recipient phone number, and variables, but adds little new semantic value beyond the schema. Baseline score of 3 is appropriate.

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 that the tool sends or schedules outbound WhatsApp template messages to recipients. The verb 'send' and resource 'WhatsApp Template' are specific. However, mentioning SMS alongside WhatsApp may cause slight confusion, and it does not explicitly distinguish this tool from siblings like 'create_broadcast' or 'list_whatsapp_templates'.

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 warns that messages are not reversible once delivered, advising to confirm the audience first. However, it lacks explicit guidance on when to use this tool versus alternatives, such as when to use broadcast vs. single template message, or when scheduling is needed. No comparisons to sibling tools are provided.

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