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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that and beyond the schema's own enum — it does not say whether demotions are reversible, whether a member can change their own role, or what happens if the target is not in the org.

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?

A single short sentence with zero filler and the key constraint (the two valid roles) front-loaded. It is efficient, though terse enough that it omits anything operationally useful.

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, the description is too thin: it says nothing about permission requirements, the optional organizationId scoping ('Approved workspace id only'), or the outcome of a successful change. Annotations and schema cover structure but not the operational context an agent needs before mutating access.

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 100%, so all three parameters (userId, role, organizationId) are already documented and the role enum is explicit. The description only restates the two role values and adds no format, defaulting, or scoping detail beyond the schema.

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 and resource ('Change a member') plus the exact role transition ('between member and admin'), which is enough to distinguish it from siblings like invite_member, remove_member, and list_members 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?

There is no guidance on when to use this versus alternatives (invite_member for a new person, remove_member to revoke access) and no stated preconditions, such as the caller needing admin privileges or the target already being in the organization.

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