Change Workspace Role

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

Beyond the destructiveHint/readOnlyHint annotations it discloses the authorization model ('Only an owner can make or change owners') and a real system invariant ('Docmost keeps at least one owner') that an agent must know before attempting a demotion. It does not mention notification side effects or whether a failed demotion produces an error versus a silent no-op.

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?

Three short sentences, front-loaded with the action and roles, then permissions, then the invariant. Every sentence carries information; only the role semantics sentence is slightly dense.

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 so return values need no explanation, and the description covers authorization, the role hierarchy, and the one-owner invariant. The main omission is any contrast with the similarly named space-level sibling, which is the most likely source of a mis-call.

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 enum already lists the three roles, so the schema carries the parameter documentation. The description adds light semantics (admin manages people and spaces; owners also manage the workspace and other owners), but the 'user' parameter is never discussed beyond what the schema says.

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 and resource ('Change a person's workspace role') and enumerates the exact values. It does not explicitly distinguish itself from the sibling change_space_member_role, so an agent must infer that 'workspace' scope differs from 'space' scope from the tool name alone.

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?

It gives a precondition ('Needs a workspace admin or owner'), which implies when the call will succeed, but never says when to prefer it over change_space_member_role or invite_people, nor any explicit exclusion. Usage is inferable rather than stated.

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