Delete WhatsApp Message

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

Annotations already indicate destructiveHint=true. The description adds that WhatsApp shows 'This message was deleted' as a placeholder, providing extra behavioral context beyond what annotations convey. No contradictions.

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 short and uses a clear structure with an Args section. The first sentence is slightly redundant with later details, but overall efficient and front-loaded.

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 destructive operation with two parameters and an output confirmation, the description covers the essential behavioral and parameter details. No output schema exists, but return value is noted. Lacks mention of idempotency or rate limits, but acceptable given the tool's simplicity.

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%. The description adds example values for contactId and explains special handling for group JIDs, but for messageId it only repeats the schema description. Meets baseline but adds limited extra meaning.

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 'Delete (unsend) a message from a contact's chat.' It uses a specific verb and resource, distinguishing it from siblings like whatsapp_edit_message and whatsapp_forward_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?

While it explains the action and outcome ('Removes the message for everyone'), it does not explicitly state when to use this tool versus alternatives or when not to use it. The context of destructive action is clear, but no direct comparison to sibling tools.

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