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

There is a clear annotation contradiction: the description includes a destructive 'delete' action, but the annotations set 'destructiveHint: false'. Additionally, the description mentions bulk support via 'message_ids' without clarifying scope or side effects, and the edit action's limitations are only partially disclosed ('recent text messages').

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 structured with bullet points but includes redundant information (delete and forward actions that have dedicated tools) and an odd 'Flattened action: edit' note. It is not as concise as it could be, though it avoids excessive verbosity.

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 essential context such as expected return values, side effects, error conditions, and how the bulk mode works. It also does not explain the relationship between the three listed actions and the actual tool behavior, leaving the agent without a complete picture of when and how to invoke the tool correctly.

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 description explains some parameters (e.g., 'for_everyone', 'to', 'text') but omits 'account' entirely and does not clarify how 'message_ids' interacts with the required 'message_id'. It also fails to specify which parameters trigger which action, leaving the mapping between actions and inputs unclear.

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 uses the vague verb 'Manage' and lists three distinct actions (delete, forward, edit) under a tool named 'whatsapp_message_edit', making the primary purpose ambiguous. It fails to clearly state that this tool is specifically for editing messages, especially given dedicated sibling tools for delete and forward.

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 explicit guidance on when to use this tool versus the dedicated 'whatsapp_message_delete' and 'whatsapp_message_forward' tools. The inclusion of delete and forward actions in the description could mislead an agent into using this tool for those unrelated operations.

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