send_whatsapp_template

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is destructive, rate limits, permissions required, or what happens if the template is invalid. It only states the action and use case.

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?

Three sentences front-loaded with the action, use case, and prerequisite. Every sentence is necessary and informative, with no wasted words.

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?

While the use case and prerequisite are clear, the description does not mention return values (no output schema) or error conditions, which are important for a sending tool. It also does not elaborate on the components parameter beyond what the schema says.

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 100%, providing baseline 3. The description adds value by explaining the process (list templates first, fill variables) and clarifying that templateName, languageCode, bodyParameters, and components are related to the template structure, going beyond the schema.

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 a pre-approved WhatsApp template message into a conversation, distinguishing it from siblings like send_whatsapp_message by specifying it is used to reach contacts outside the 24-hour window.

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 explicitly says to use this tool outside the 24-hour window and provides a prerequisite to call list_whatsapp_templates first, but does not explicitly state when not to use it or name the alternative (send_whatsapp_message).

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