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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond them: no mention that a sent message cannot be recalled, no rate/anti-ban limits, no requirement that instance_id refer to a connected instance. For a destructive, non-idempotent mutation the description contributes zero extra signal.

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?

A single front-loaded sentence with no filler. It is efficient but arguably under-specified rather than deliberately tight; there is room for one clause of usage guidance without bloat.

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?

With 5 parameters, full schema coverage, and no output schema, the mechanical information is present. However, for a destructive messaging action the description omits the operational prerequisites (connected instance, chat ID format caveats) and the fact that sends are irreversible, leaving a meaningful gap.

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%, including formats for chat_id (user vs group JID), so the schema carries parameter meaning. The description adds no additional semantics such as how quoted_message_id interacts with the message body. Baseline 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?

Specific verb+resource ("Send a text message via WhatsApp") that distinguishes it from media siblings like whatsapp_send_file, whatsapp_send_location, and whatsapp_send_contact. It stops short of naming those siblings explicitly, so differentiation is inferred rather than stated.

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 gives no when-to-use context, no prerequisites (e.g. an instance must be connected and in a valid state), and no routing hints toward the other send_* tools. An agent must infer entirely from the tool name which send variant to pick.

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