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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the mutation risk profile is known without the description. The description adds the restriction that only admin/member roles are settable and that ownership transfer is out of scope, but says nothing about what happens to the member's prior role, required caller permissions, or reversibility — modest added value beyond annotations.

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, zero filler, with the core action front-loaded and the scope limitation tucked into a parenthetical. Every clause earns its place.

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 two-parameter mutation with full schema coverage, rich annotations and an output schema, the description supplies the scope boundary an agent needs. The only remaining gap is caller-permission expectations, which are not stated.

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% and the role enum is defined in the schema, so the schema already documents both parameters. The description restates the enum values ('admin or member') but adds no syntax, format, or constraint 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 ('Set') plus resource ('account member's role') and enumerates the allowed target values. It implicitly separates itself from the sibling update_project_member_role by scoping to account members, so an agent can pick the right tool without opening either 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?

Gives clear context for the tool's scope and adds one explicit exclusion ('Ownership transfer is not available through this connector'), which is genuine when-not guidance. It stops short of naming the alternative tool for ownership transfer or stating the permission prerequisite (e.g. caller must be an account admin), so it is not a full 5.

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