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

Annotations already declare idempotentHint=true and destructiveHint=true, so the safety profile is covered. The description adds genuine context beyond that: it specifies the authorization prerequisites (team admin, team owner, or org owner/admin), which an agent needs to predict failures. It stops short of saying what happens to the member's prior access or what an unauthorized call returns.

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?

Three tight sentences: the action first, the role vocabulary second, the authorization constraint last. Every sentence earns its place and nothing is padded.

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-parameter mutation with no output schema and annotations that already cover safety hints, the description supplies the two things an agent most needs: role semantics and permission prerequisites. Only edge-case behavior (failure modes, effect on existing access) is unstated, which is a minor gap.

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%, so the baseline is 3. The description exceeds it by defining the semantics of each enum value (team_admin manages the team, editor edits team flows, viewer opens only), which the schema enumerates but does not explain. It does not add anything for team_id or email, both of which the schema already documents.

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 the role of one person on a team") and even enumerates the role values, so the agent knows exactly what state transition this performs. It does not, however, differentiate itself from the similarly named sibling set_member_role or from add_team_member, leaving that disambiguation to inference.

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?

The description implies usage (changing an existing team member's role) but gives no explicit when-to-use guidance versus set_member_role, add_team_member, or remove_team_member. Usage is inferable from the purpose statement rather than stated as a rule.

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