Remove Team Member

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

Adds critical behavioral details beyond annotations: member immediately loses access, created records are preserved, and special rule about workspace owner. Complements destructiveHint and readOnlyHint annotations with concrete 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?

Concise sentences with front-loaded main action. Bilingual repetition (Spanish and English) adds length but is appropriate for multi-language context. Every sentence conveys unique information without fluff.

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?

Fully covers the tool's destructive nature, side effects (record preservation), edge case (owner), and parameter requirement (confirm). With existing output schema and clear sibling list, agent has sufficient information to decide and invoke correctly.

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 describes both parameters (memberId and confirm) with 100% coverage. Description adds value by explaining why confirm is required (prevent accidental removal) and that it must be true, enhancing the schema's basic description.

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?

Clearly states 'Remove a member from the workspace' with specific verb (remove) and resource (team member). Distinguishes from sibling tools like invite_team_member, update_team_member_role, and list_team_members.

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 explicit context: when to use (removing a member), when not to use (cannot remove workspace owner), and prerequisite (transfer ownership first). Also specifies required confirm parameter to prevent accidental removal. Could explicitly name alternatives but current guidance is sufficient.

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