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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds real value beyond that: authorization requirements (owner/admin only), the ownership-grant restriction, the self-modification ban, and the 'keeps at least one owner' invariant. It stops short of describing the response or side effects like notification, so it is not exhaustive.

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?

Five short, front-loaded sentences, each contributing a distinct rule; nothing is repetitive or filler. The action is stated first and constraints follow, matching how an agent reads.

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 permission-sensitive mutation with no output schema and full schema coverage, the description supplies the authorization model and invariants an agent needs. It omits only minor details (error behavior when inviting an unknown email, downstream effects), which the annotations partially cover.

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 parameter carries an enum, so the schema already documents all three parameters. The description's mention of owner/admin/member merely restates the enum and adds no format or syntax detail for org_id or email.

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's organization role') and enumerates the target values, so an agent knows exactly what it does. The 'organization' qualifier naturally distinguishes it from the sibling set_team_member_role, which handles team roles.

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 preconditions and exclusions: only owners/admins may call it, only an owner can grant/alter ownership, no self-changes. These constraints route the agent well, though it never explicitly names the alternative tool for team-scoped changes (set_team_member_role).

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