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

Annotations already mark the tool as destructive and not read-only. The description adds useful context beyond that: an authorization requirement (workspace ownership) and an expectation to confirm with the user. It does not contradict the annotations, though it could mention irreversibility or re-invitation.

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?

Two short sentences with no wasted words. The action and scope are front-loaded, and the critical confirmation instruction is included without 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?

For a two-parameter destructive operation with full schema coverage and clear annotations, the description supplies the key non-obvious context: ownership and prior confirmation. It leaves out only minor details such as the post-removal outcome, but nothing essential is missing for selecting and calling the tool.

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%, so both parameters are already fully explained, including the optional workspace_id default and the source of member_user_id. The description adds no additional parameter-level detail, placing it at the baseline for fully-covered schemas.

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 the specific verb 'Remove' with a clear object ('a user from a workspace') and states the ownership prerequisite. This makes it readily distinguishable from sibling tools like invite_workspace_member or cancel_workspace_invitation.

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 clearly implies when to use the tool: when removing an existing member from a workspace you own. It also provides explicit operational guidance ('Confirm with the user first'), though it does not explicitly contrast itself with invite_workspace_member or cancel_workspace_invitation.

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