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

Annotations indicate readOnlyHint=false, destructiveHint=false, but the description does not add much beyond that. It mentions the admin requirement and the action types, but does not disclose potential side effects (e.g., whether demoting is reversible, if it affects group state) or any rate limits. With annotations present, the bar is lower, but the description could add more context about what happens when demoting.

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 concise, with two sentences plus a flattened action note. It front-loads the purpose and includes key details about users format. The '[Flattened action: demote]' is a bit redundant but not harmful. No wasted words.

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?

Given the tool has 3 parameters, no output schema, and low schema coverage, the description provides some essential info (admin requirement, user format, action list) but lacks details on group_jid and account parameters, and does not describe return values or error conditions. It is adequate but not complete for a tool with this complexity.

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 that 'users' accepts 1-50 phone numbers (+E164) or JIDs, which adds meaning. However, it does not explain 'group_jid' or 'account' parameters, leaving them undocumented. The description partially compensates but leaves gaps for two of three 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?

The description clearly states the tool manages WhatsApp group participants with specific actions (remove, promote, demote, add) and the flattened action is 'demote'. It distinguishes from siblings like whatsapp_group_participants_add, promote, and remove by specifying the demote action, though it could be more explicit that this tool is specifically for demoting admins.

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 mentions the connected account must be a group admin, which is a key prerequisite. It lists the actions but does not explicitly state when to use this tool versus the sibling tools for add/promote/remove. The flattened action 'demote' implies usage, but no explicit alternatives or exclusions are given.

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