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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses important behavioral details: it removes every other member, leaves the group, requires admin privileges, and explains the platform limitation behind this approach. This is exactly the kind of context an agent needs to anticipate side effects.

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 three tight sentences with the action front-loaded, followed by the operational mechanics and a necessary caveat. Every sentence contributes information; there is no padding.

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?

With destructive and idempotency annotations plus an output schema already provided, the description covers the non-obvious aspects: admin requirement, member removal, and the leave step. It could additionally note irreversibility or member notifications, but these are minor given the existing annotations and output schema.

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% and the schema already provides provenance hints ('as returned by wa_list_groups', 'as returned by wa_list_accounts'). The tool description adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource ('Delete a WhatsApp group') and precisely defines what that means in WhatsApp terms: remove every other member and leave. This distinguishes it clearly from sibling tools like wa_delete_message and wa_delete_webhook, which operate on different resources.

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?

The description clearly communicates the context for use: the account must be a group admin, and because WhatsApp has no true group-delete, this tool's approach is to empty and exit. It does not explicitly contrast with alternatives like wa_remove_participants or wa_leave_chat, but the intended use is unmistakable.

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