whatsapp_forward_message

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

The description is extremely minimal and does not disclose any behavioral traits beyond the basic operation. With no annotations, the description carries the full burden but fails to mention side effects, permissions, or constraints (e.g., can it forward to groups? Does it require the message to belong to the user?).

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 extremely concise: one sentence plus two parameter hints. No redundant information; every word serves a purpose.

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?

The description lacks completeness given the tool's complexity and number of siblings. It does not explain return values (despite having an output schema), error handling, or conditions under which the operation might fail. Critical context is missing for an agent to use the tool effectively.

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 schema has 0% description coverage, so the description must compensate. It adds brief explanatory notes: 'message_id: original msg' and 'to_phone: number or group JID', which clarify the parameter roles beyond the schema titles. However, it does not specify format or validation requirements.

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 action ('Forward a message to another chat') and identifies the key parameters (message_id, to_phone). However, it does not fully differentiate from similar tools like whatsapp_reply_message or whatsapp_send_text, which could also send messages to chats.

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 guidance is provided on when to use this tool versus alternatives such as whatsapp_send_text or whatsapp_reply_message. There is no mention of prerequisites, limitations, or context for using forward vs. other messaging actions.

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