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

Annotations provide only false hints (readOnly, idempotent, destructive all false), so the description carries the burden. It adds the permission requirement (account must be a group admin), which is useful context. However, it does not disclose behavior for edge cases (e.g., non-admin members) or side effects relative to removal, so it gives only partial transparency.

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?

Two short sentences with no redundancy: the first defines the action, the second states a necessary precondition. Both earn their place, and the description is front-loaded with the primary purpose.

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 mutation tool with full schema coverage and an output schema, the description covers the essential prerequisite but leaves ambiguity about edge cases (e.g., demoting a non-admin, self-demotion) and the relationship to sibling tools. It is adequate but not thorough.

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 100%, and each parameter is described with references to related tools (wa_list_groups, wa_list_accounts). The description adds no extra 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 uses a specific verb ('demote'), identifies the resource (group participants), and specifies the outcome ('back to ordinary members'). It clearly implies the opposite of promote_participants but does not explicitly name any sibling tool, so it misses the highest mark for differentiation.

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 only guidance is the prerequisite 'The account must be a group admin,' which is a precondition for calling the tool, not a selection criterion. It does not mention when to use this tool over alternatives like remove_participants or promote_participants, leaving that inference to the agent.

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