Send WhatsApp message

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

No annotations are provided, so the description carries the behavioral burden. It adds a consent requirement ('Confirm the recipient') and optional reply behavior, but does not mention immediate delivery, inability to unsend, or whether a sent confirmation or error is returned.

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 short sentences with no filler; the core action is first, the safety guard second, and the optional behavior third. Every sentence earns its place.

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?

For a low-complexity send operation, the essential call information is covered: what to send, the confirmation prerequisite, and optional quoting. With no output schema, it could briefly state expected return feedback such as message id or status, but that is not critical for invoking the tool.

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?

The input schema already describes all three parameters well, including acceptable values for 'to' and the meaning of reply_to. The description adds only limited new information by labeling reply_to as optional and confirming the 'by id' semantics.

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?

States a specific action ('Send a text message') on a distinct resource, and the optional quote behavior differentiates it from file transfer. However, it does not explicitly distinguish send_message from broadcast_message, both of which may send text.

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?

Explicitly instructs the agent to confirm the recipient with the user before calling, which is a clear when-to-use guard. It does not name alternatives like send_file or broadcast_message, so the agent must infer when this tool is preferred.

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