Remove Team Member

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

Discloses important behavioral traits beyond annotations: immediate loss of access, preservation of created records, restriction on removing owner, and confirmation requirement. Annotations already indicate destructive and idempotent, but description adds concrete details.

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?

Very concise: 4 sentences in English, front-loaded with the main action. Bilingual inclusion is justified for audience. No unnecessary words.

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 low complexity (2 params), annotations, and presence of output schema (context signal), the description covers all essential behavioral aspects: access loss, record preservation, owner restriction, confirmation requirement. No gaps.

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 already covers 100% of parameters with descriptions. The description reinforces confirm as a safety measure but does not add significant new meaning beyond the schema for either parameter.

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' with specific verb and resource. It distinguishes from sibling tools like invite_team_member and update_team_member_role by focusing on removal and noting preservation of records.

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?

Provides clear usage context: removing a member, immediate loss of access, cannot remove owner (requires transfer first), and requires confirm=true. Lacks explicit alternatives or prerequisites like permissions, but gives strong guidance.

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