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

With no annotations, the description carries the full behavioral burden and does so excellently. It discloses that the action only stages a request, that the owner must approve in a browser with their agent PIN, that the change is not immediate, and that the PIN must never be requested in chat.

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?

Every sentence earns its place: the action, role definitions, the self-role restriction, the staged approval flow, and the security warning. The description is dense but not bloated, with the most important operational detail—staging—clearly emphasized.

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?

The description covers the asynchronous approval process, security constraints, role semantics, and workspace ambiguity. It doesn't explicitly state that the email must belong to an existing member or how to check staged-request status, but an agent has enough to invoke the tool correctly and set user expectations.

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 documents all parameters at 100% coverage, and the description adds meaningful semantics: it explains the practical meaning of each role and clarifies that 'workspace' is only needed when the user owns more than one, pointing to list_workspaces as the discovery mechanism.

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 states a specific action—changing a member's workspace role to admin, member, or owner—and defines what each role means. This clearly differentiates it from sibling tools like assign_access_role or list_workspace_members.

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 gives clear context: the caller must own the workspace, the target must be an existing member, and the agent cannot change its own role. It doesn't explicitly name alternative tools, but the staged-approval flow and ownership requirement make the use case clear.

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