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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: the owner-only authorization constraint, the two supported auth mechanisms, and a security warning that key arguments may persist in task history. It does not restate the idempotency guarantee already implied by the request_id parameter.

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?

Purpose is front-loaded in the opening sentence, followed by authorization requirements and then auth mechanics. The final security sentence is somewhat verbose and duplicates the key parameter description in the schema, but it is arguably load-bearing for a credential field.

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 5-parameter mutation tool with no output schema, the description covers purpose, permission constraints, auth options and idempotency context adequately. It omits any statement of the response shape or what happens to prior roles, but nothing essential to invoking it correctly is missing.

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 80%, so the schema already documents key, role, account_id and request_id with meaningful text. The description largely repeats the schema's role and account_id semantics rather than adding new meaning, so the baseline of 3 applies.

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 first sentence gives a specific verb and resource ('Set a member's role to moderator or member') and enumerates the two allowed values, so the agent knows exactly what the tool mutates. It implicitly separates itself from the removal sibling (community_member_remove) by framing the operation as a role assignment, though it never names a sibling explicitly.

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 supplies prerequisites ('Only the community owner can assign or remove moderator status; requires account scope and the target member's account_id'), which tells the agent when the call will succeed. It never states when to prefer this over community_member_remove or community_post_moderate, so the usage guidance is implied rather than comparative.

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