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

With no annotations, the description carries the full burden and does so well. It discloses immediate loss of mailbox access, reversibility via re-invitation, the inability to remove yourself, the two-step browser approval flow, and the critical safety rule about never asking for or accepting the PIN 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?

The description is four sentences with no wasted words. It front-loads the core action, then gives consequences, workflow, and a safety guardrail. Every sentence contributes essential information for correct and safe invocation.

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 simple two-parameter tool with no output schema and no annotations, the description is complete. It covers what the tool does, when it applies, what happens immediately, the approval workflow, and a critical security constraint. Nothing needed 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% for both parameters, so the baseline is 3. The description adds value by clarifying that the email must be someone else's ('You can't remove yourself this way') and reinforces the workspace ownership requirement, going slightly beyond the schema's simple 'The member's email' and 'Which workspace' descriptions.

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 ('Remove someone from a workspace you own') with a clear resource and scope. It also distinguishes itself by noting self-removal is not possible and that the action only stages a request, which separates it from direct removal or invitation tools.

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: use it for members in a workspace you own, and it explicitly says you cannot remove yourself. It also explains the approval workflow and warns against handling PINs in chat. However, it does not explicitly name alternative tools like pause_member or cancel_invitation, so it falls short of full alternative-based guidance.

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