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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known from structured data. The description adds nothing beyond that: it does not say what is destroyed (group, message history, member associations), whether the deletion is permanent for all participants, or what authorization the administering number needs.

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?

A single short sentence with the action and scope front-loaded and no filler. It is efficient, though the extreme brevity is partly why other dimensions are thin.

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, irreversible-feeling group operation with no output schema and one undocumented parameter, the description is minimally adequate. Annotations carry the destructive flag, but the agent is not told the blast radius of the deletion or the required admin role.

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 coverage is only 67% (group_id has no description), so the description would need to compensate. It says nothing about any of the three parameters, and the admin wording only loosely gestures at phone_number_id/profile_id without adding format or sourcing detail.

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 WhatsApp group') and adds a meaningful scope qualifier ('the phone number administers'), which separates it from sibling mutations like whatsapp_group_update or whatsapp_group_participants_remove. It does not, however, explicitly name any sibling tool, so differentiation still requires the agent to compare names.

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 phrase 'the phone number administers' implies a precondition (the profile/number must be a group admin), which is a useful usage constraint. Beyond that there is no when-to-use guidance, no exclusions, and no mention of alternatives such as removing participants or leaving the group.

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