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

The annotations already flag destructiveHint=true, but the description adds critical behavior beyond them: the permission matrix, the self-removal effect, the ownership-transfer requirement, and the need for user confirmation. These are exactly the operational details an agent needs before invoking a destructive membership mutation.

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 front-loaded and dense with useful constraints, with no wasted preamble. There is minor repetition of the schema's note that user_id comes from list_workspace_members, which keeps it just short of perfect conciseness.

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 with no output schema, the description covers what the tool does, who may call it, when it is forbidden, self-removal behavior, and the confirmation requirement. Nothing essential for correct invocation is missing.

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%, so the schema already documents all three parameters, including idempotency_key. The description adds meaningful semantics for user_id by explaining that passing one's own user_id means leaving the workspace and that owners must transfer ownership first.

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 uses a specific verb and resource: it removes a team member from a workspace and explains the effect, that they lose access. This clearly distinguishes it from siblings like invite_workspace_member, revoke_workspace_invitation, and update_workspace_member_role.

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 explicit preconditions and exclusions: owners/admins can remove others, admins cannot remove owners or admins, and the owner cannot be removed. It also tells the agent to confirm destructively with the user and explains the self-removal case and ownership-transfer prerequisite.

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