Forward WhatsApp Message

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

Annotations (readOnlyHint=false) confirm this is a write operation. The description adds behavioral context: the forwarded message labels itself, preserves attribution, and returns a confirmation with the new message ID. No contradictions with annotations.

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 (3 short paragraphs) and well-structured: a one-sentence purpose, a line about labeling, and bullet-like parameter explanations. No redundant 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?

For a simple 2-param tool, the description covers all essential aspects: purpose, parameter sourcing, expected label behavior, and return value. No output schema is needed given the simple confirmation format.

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 baseline is 3. The description adds meaningful guidance beyond the schema: how to obtain contactId (via whatsapp_list_contacts) and messageId (from whatsapp_read_messages), and explains the ID format and stability across @c.us↔@lid flips.

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's purpose: 'Forward a message from one chat to another contact.' This is a specific verb+resource pair that distinguishes it from sibling tools like whatsapp_send_text (sends new message) or whatsapp_delete_message (deletes message).

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 explains what forwarding does (shows 'Forwarded' label, preserves attribution) but does not explicitly state when to use this tool vs alternatives like sending a new message or editing. Usage context is implied rather than explicit, lacking when-not-to-use guidance.

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