whatsapp_delete_message

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

Goes well beyond the annotations: it discloses irreversibility ('cannot be undone'), the visible side effect for other participants, and the authorization scope (own messages or admin powers). This is exactly the 'what gets destroyed / auth needs' context the annotations alone do not supply.

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?

Front-loads the action and warning, then the routing alternative, then the scope constraint. Dense and well ordered; only the trailing 'Returns a success confirmation' is low-value filler.

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 destructive tool with no output schema, it covers action, irreversibility, side effects, permissions, and the return signal. Nothing an agent needs to call it safely is missing.

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%, so chatId, senderId, and messageId are already documented in the schema. The description adds no format or syntax detail beyond it, which matches the baseline 3 for fully covered schemas.

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?

States a specific verb and resource (delete a message for everyone) and immediately distinguishes itself from the sibling whatsapp_delete_message_for_me. An agent can tell these two apart without opening either schema.

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?

Explicitly names the alternative and the condition that selects it ('To hide a message only on this account, use whatsapp_delete_message_for_me'). It also states the prerequisite for using this tool: own messages, or others' messages when acting as group admin.

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