whatsapp_delete_message

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

No annotations provided, so description carries full burden. Warns 'DESTRUCTIVE' and explains revocation behavior, but lacks details on error handling, undo possibility, or system logging. Adequate but not rich.

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?

Very concise with only three sentences. Uses symbols for emphasis. Every sentence provides unique information without waste.

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 4 parameters and an output schema, the description minimally covers key aspects. Could include hints on how to obtain message_id or handle failures, but output schema reduces need for return info.

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 0%, so description must compensate. It explains 'confirmed' and 'everyone', but 'phone' and 'message_id' are not elaborated. Adds value for two out of four parameters.

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?

Clear verb 'delete' and resource 'message' make the tool's purpose immediately obvious. Distinguishes from siblings like send, get, or react tools.

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 states 'confirmed=True required — always ask user first' and explains the 'everyone' parameter. Provides clear guidance on when to use (with confirmation). Could mention alternatives (like deleting for self only) but is sufficient.

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