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

With no annotations provided, the description fully carries the behavioral burden. It discloses authentication requirements (Editor/owner), the sole-owner protection rule, no-op behavior, and the emitted event `member.role_changed` with from/to roles. This significantly goes beyond the structured schema, offering complete transparency about side effects and constraints.

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?

The description is compact, with five short sentences each delivering distinct, high-value information: operation, permission requirements, edge case, no-op behavior, and event output. No filler or repetition of schema details; every sentence earns its place.

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 mutation tool with only three parameters, no output schema, and no annotations, the description covers all critical contextual aspects: required permissions, owner-specific restrictions, success semantics (no-op), and the resulting event. This is complete enough for an agent to invoke the tool safely and effectively, including knowing when to avoid it (sole-owner demotion).

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?

The schema already provides 100% parameter descriptions, including the slug format, member_id source, and role enum. The tool description does not add new parameter-level meaning beyond the schema, though it does contextualize role transitions. This is a case where the structured data covers the semantics, and the description adds no extra parameter 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?

The description opens with 'Change an existing workspace member's role,' naming a specific verb, resource, and operation that distinguishes it from sibling tools like remove_workspace_member (removal) and share_workspace (inviting/sharing). This clear action and resource scope leaves no ambiguity about the tool's function.

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 provides explicit usage conditions: caller must have Editor role, owner-tier transitions require an owner caller, demoting the sole owner is blocked with a concrete workaround ('promote someone else to owner first'), and the operation is a no-op when the role is unchanged. These are precise when-to-use and when-not-to-use instructions.

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