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 safety profile is covered. The description adds only a restatement of the role enum found in the schema, and says nothing about whether the new role replaces the old one, what permission changes ripple out, or what authorization is required.

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?

A single short sentence with no wasted words, front-loaded with the action and resource. It is efficient, though the extreme brevity leaves explanatory gaps rather than being an example of rich concision.

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?

An output schema exists and annotations cover the mutation safety profile, so return values and danger signals are handled elsewhere. What is missing is the prerequisite context (existing membership), the effect on the prior role, and any routing to sibling role-management tools, making this the minimum viable definition.

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 fully documents all three required parameters. The description merely repeats the enum values, adding no syntax, format, or identity-resolution guidance beyond what the schema provides.

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), resource (project role) and the exact enum values, so the agent knows it mutates a member's project-level role. The 'project' qualifier implicitly separates it from update_account_member_role and update_project, but it never names those siblings explicitly.

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?

No indication of when to use this versus update_account_member_role or remove_project_member, and no stated prerequisites (the user must already be a project member). The agent must infer the routing from the tool name alone.

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