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

The description substantially enriches the annotations: destructiveHint is true, and the description specifies concrete destructive consequences (demotion cancels active builds and pauses armed project agents, ownership transfer changes the current owner's authority). It also explains the explicit confirmation requirement, going well beyond the structured data.

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?

Two tight sentences deliver the core action first and then the critical consequences. Every clause adds relevant information, and there is no filler or repetition of schema details.

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 four required parameters and no output schema, the description conveys the essential call context: role options, confirmation requirement, and the significant side effects. It omits an expected return behavior, but the description is otherwise sufficient for an agent to invoke the tool safely and correctly.

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?

With schema description coverage at only 25%, the description partially compensates by explaining the role enum semantics (collaborator/viewer vs. ownership transfer) and reinforcing that confirm is required. However, it does not add meaningful detail about project_id or member_id beyond what the schema structures imply, leaving gaps for those parameters.

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 uses a specific verb ('Change') and a clear resource ('one exact member'), and explicitly lists the possible outcomes: collaborator, viewer, or ownership transfer. This clearly distinguishes the tool from sibling tools like invite_project_member or remove_project_member.

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 conveys the context in which the tool is appropriate—changing an existing member's role, including demotions and ownership transfer—but it does not explicitly say when to use this tool instead of alternatives, nor does it name exclusions. Usage is implied rather than stated.

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