Remove Team Member

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

Beyond annotations (destructiveHint=true), the description adds critical behavior: immediate loss of access, preservation of created records, and the owner restriction. This enriches the agent's understanding of side effects.

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 bilingual (English/Spanish), which is slightly longer but necessary. It is front-loaded with the main action and key points. Could be trimmed to single language if not needed, but still efficient.

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?

Given the destructive nature and presence of output schema (not shown), the description covers all essential aspects: immediate effect, data preservation, owner constraint, and confirmation requirement. No gaps identified.

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 baseline is 3. The description reiterates the 'confirm' requirement but adds no new semantic detail beyond the schema descriptions. No additional parameter context is provided.

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 clearly states the action ('Remove a member from the workspace'), specifies the consequences (immediate access loss, record preservation), and distinguishes itself from sibling tools like 'invite_team_member' and 'update_team_member_role' by focusing on removal.

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 explicitly says when to use (to remove a member) and when not to (cannot remove workspace owner, requiring ownership transfer first). It also mandates 'confirm=true' to prevent accidental removal, providing clear usage direction.

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