whatsapp_send_message

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

With no annotations, the description carries full burden for behavioral disclosure. 'Send' implies a mutation operation, but there is no mention of prerequisites (e.g., an active chat), permission needs, or consequences (e.g., message history updates). The agent is left guessing about the tool's side effects.

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 a single short sentence, which is concise, but it lacks necessary detail. Conciseness should not come at the cost of completeness, and here it fails to provide adequate information.

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 of sending a message (requiring recipient and content), the description is entirely inadequate. Without parameters, output schema, or annotations, the agent has no guidance on how to use the tool effectively. The description is essentially a placeholder.

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 is empty, and the description does not explain that no parameters are needed or clarify how to specify recipient and content. For a messaging tool, this is a critical omission; the description adds zero semantic value 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 'Send a WhatsApp message' is a near-tautology of the tool name, providing no additional clarity on the type of message or how the operation is performed. It fails to differentiate from sibling tools like whatsapp_send_file.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as whatsapp_send_file or whatsapp_read_messages, leaving the agent without decision support.

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