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

Beyond annotations (destructiveHint=true, idempotentHint=false), the description adds two meaningful behavioral facts: the admin-only authorization requirement and that the change is pending owner approval rather than immediate. It still doesn't clarify whether the role takes effect now or only after approval, or what happens to the call's result.

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 tight sentences with the core action front-loaded and prerequisites trailing. No filler or restatement of the title.

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 3-required-param mutation with no output schema, the description covers the key concerns: authorization and the approval gate. It could go further on the outcome (immediate vs queued) and failure behavior, but nothing critical is absent.

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 the enum is fully documented in the schema, so the schema already carries parameter meaning. The description adds no format, constraint, or linkage detail (e.g., that membership_id must come from list_members) beyond what's structured.

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 (set role) and enumerates the exact target roles (admin, moderator, member), making the mutation unambiguous. An agent can distinguish this from remove_member or ban_member without opening the schema.

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?

'Admins only' gives a clear permission precondition and 'Waits for the owner's approval' signals an async gated flow. It does not name alternative tools (e.g., ban_member vs demote) or say when not to use it, so it falls short of a 5.

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