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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds real value beyond that: access termination is immediate and explicitly includes chat connections, plus the last-owner guard and the owner-only authorization requirement. It does not say whether the removed user's owned resources (projects, domains) are affected, which is the main remaining behavioral gap.

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 sentences, both load-bearing, with the primary effect front-loaded and the constraints following. No filler, no restatement of the title.

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 single-parameter destructive tool with annotations covering the safety hints and no output schema, the description covers effect, immediacy, authorization, and the key guard condition. The only notable omission is downstream impact on resources the removed member owned.

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?

There is a single parameter with 100% schema description coverage, so the schema already carries the parameter burden and the baseline of 3 applies. The description adds no detail about user_id format, sourcing (e.g., from list_members), or whether it accepts emails.

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 a specific verb and resource ("Remove a member from the workspace"), which clearly separates it from neighbors like cancel_invite (pending invites) and set_member_role (role change). It stops short of naming any sibling explicitly, so the distinction is inferable rather than stated.

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 supplies useful preconditions — "Workspace owners only" and "The last owner can't be removed" — which tell the agent about permission requirements and a hard failure case. It does not, however, say when to choose this over cancel_invite or set_member_role, so routing between the member-management siblings is left to inference.

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