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

Goes well beyond the annotations (readOnlyHint false, idempotent true, destructiveHint false) by disclosing that the change takes effect immediately for already-issued tokens, that the creator is permanently owner, and that self-demotion is irreversible. These are consequential behaviors an agent could not infer from structured fields.

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?

Front-loads the critical constraint (Owner only) and each sentence carries distinct information. It runs slightly long, with the token-behavior and self-demotion clauses both present, but neither is filler.

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?

No output schema exists, and the description never states what is returned or whether the call fails silently on the forbidden cases, which is a minor gap. For a two-parameter mutation it otherwise covers permissions, side effects, and irreversible cases thoroughly.

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% and the enum is already defined, so the baseline is 3; the description adds real value by explaining the operational meaning of the roles and pointing to list_members for user_id. It does not, however, add format or edge-case detail beyond that.

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 (change), resource (one member's role), scope (this workspace), and the exact target values (editor or viewer). An agent can immediately distinguish it from add_member, remove_member, and invite_teammate without opening any 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?

Explicit when/when-not guidance: owner-only, the workspace creator cannot be changed, and you cannot change your own role. It even explains the workaround (have another owner do it) and where to source the input (user_id from list_members), leaving nothing to inference.

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