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

Annotations declare destructiveHint=false, but the description describes removing participants from a group, which is inherently destructive. This contradiction is a serious issue. No other behavioral details (e.g., irreversibility, permissions beyond admin) are disclosed.

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 verbose and includes irrelevant actions, complicating the actual single-purpose tool. The 'Flattened action' line is confusing and not a natural part of the description. It lacks clear organization.

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 mutation tool with no output schema and minimal annotations, the description omits critical details like what happens after removal (e.g., irreversible?), error conditions, or response format. It only covers admin requirement and user list format.

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 the description must compensate. It explains 'users' (1-50 phone numbers or JIDs) but leaves 'group_jid' and 'account' undefined. This is insufficient for proper usage.

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 lists multiple actions (remove, promote, demote, add) despite the tool being specifically for removal (per name and 'Flattened action: remove'), making the purpose ambiguous and misleading. It doesn't clearly state that this tool only removes participants.

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?

Only mentions a prerequisite (group admin) and user count range, but does not explain when to use this tool versus the dedicated sibling tools for add, promote, and demote. It also incorrectly suggests the tool can perform other actions.

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