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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the mutation profile is covered. The description confirms the effect is limited to revoking admin rights (the participant stays in the group), but adds nothing about permission requirements, reversibility, or error conditions for a destructive operation.

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 six-word sentence, front-loaded with the verb and effect. Nothing redundant or padded.

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 three-parameter mutation with fully described schema and rich annotations, the description is minimally adequate. However, for a destructive admin-level operation it omits prerequisites (caller privilege, connected instance) and the fact that failure occurs if the target is not an admin, leaving gaps an agent would want covered.

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% with all three required parameters (instance_id, group_id, participant_chat_id) documented including ID formats, so the baseline of 3 applies. The description adds no additional meaning, such as that participant_chat_id must currently be an admin.

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 ('Revoke') and resource ('admin rights') scoped to 'a group member', which clearly separates it from the sibling whatsapp_remove_group_participant (removes membership) and whatsapp_set_group_admin (grants). The distinction from set_group_admin is only implicit via the tool name, not stated in prose.

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 gives no when-to-use guidance, no mention of alternatives, and no prerequisites such as the caller needing to be an admin of the group or the instance needing to be connected. An agent must infer all conditions for safe use.

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