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

Annotations already mark readOnlyHint=false, indicating a write operation, and the description confirms this with 'Change the role.' It goes beyond annotations by disclosing failure conditions (accepted/declined invitations are rejected) and permission requirements (Manager role or above), adding valuable behavioral context without contradicting the 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?

The description is two sentences long and front-loaded with the core purpose. The first sentence states the action, and the second covers constraints and permissions. Every word earns its place; no fluff or repetition.

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?

Despite having no output schema, the description covers the essential aspects: what the tool does, when it can be used (pending invites only), and who can use it (Manager+). It does not mention the return value or side effects, but for a simple role-update operation with good annotations and full schema coverage, this is reasonably complete. A minor gap is lack of any post-update behavior, but not critical.

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%: each parameter (id, role, team_id) has a detailed description in the schema. The tool description does not add any further parameter-level information, so it neither improves nor degrades the schema's clarity. 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?

The description clearly states the action: 'Change the role on a pending team invitation.' It names the specific resource (pending team invitation) and the attribute being modified (role). This distinguishes it from sibling tools like createTeamInvite, deleteTeamInvite, listTeamInvites, and updateTeamMemberRole.

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 provides explicit when-to-use guidance: 'Only pending invitations can be updated — one already accepted or declined is rejected.' It also specifies the required permission ('Requires the Manager role or above'). It does not name alternative tools, but the constraints are clear enough to guide appropriate usage.

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