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

Adds meaningful behavioral context beyond annotations: roleSlug null removes the grant, expectedVersion is an optimistic-concurrency guard sourced from team/workspace-members views, and the caller should refresh after a conflict. These details align with the destructiveHint=true and idempotentHint=true annotations rather than contradicting them.

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: the mutation and null behavior are front-loaded, followed by the version/conflict guidance. Every clause carries operational meaning.

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 the critical semantics: single-member scope, null removal, optimistic concurrency, and conflict recovery. It could mention permission requirements or irreversibility more explicitly, but it is sufficient to call the tool correctly given the annotations.

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 80%, so most parameters are already documented. The description still adds value by explaining that roleSlug null removes the grant and by reinforcing where expectedVersion must come from, though it does not document every field in detail.

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 mutation: "Change ONE member's workspace role," and clarifies the null-roleSlug behavior. This distinguishes it from sibling operations like company_offboard_member, company_invite_member, and listing tools, so an agent can select it without opening the schema.

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?

Gives clear operational guidance: use the current membership version and available actions from the team or workspace-members view, and refresh after a conflict. It does not explicitly name alternatives for adding or removing members, but the prerequisites and conflict-retry path are clearly stated.

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