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

Annotations already flag destructive/openWorld/non-idempotent, but the description adds valuable context beyond them: the operation emails the member, returns old and new role, and states strict authorization constraints. This is exactly the kind of side-effect and permission disclosure the annotations don't provide.

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?

Front-loaded with the use case and alternatives, then permission rules. It is a single dense paragraph with little waste, though the sentence run-on about owners/admins is slightly heavy; still efficient overall.

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 destructive mutation tool with no output schema, the description covers when to use it, alternatives, permission gates, side effects (email notification), and return value (old/new role). Nothing an agent needs to call 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 100% and the schema already describes the role enum values and the scope enum in detail. The description echoes 'admin, editor or viewer' and the scope idea but adds no format or default semantics beyond what the schema states (e.g., 'Leave out to keep the member's current scope' is already in the schema). Baseline 3 is appropriate.

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+resource ('change a member's role'), names the accepted roles, and mentions scope ('cover different monitors'). It explicitly distinguishes itself from invite_member and member removal, so an agent can identify it without opening siblings.

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?

Explicitly says when to use it ('when the user wants a team member to have a different role') and when not to: inviting (use invite_member) and removing (done in the dashboard). It also spells out permission preconditions (owners and admins only, no self-role changes, no changing the owner, admin changes only by owner).

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