Remove Organization Member

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

The description is consistent with the destructiveHint annotation, but it adds no additional behavioral context beyond what the annotation already conveys. There is no mention of irreversibility, cascading effects, or required permissions.

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 extremely concise, consisting of a single front-loaded sentence with no extraneous words. However, it may be too brief to provide sufficient context for an AI agent.

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 destructive tool, the description is incomplete. It does not explain what happens after removal (e.g., whether the user loses all access, if their data is retained, or if notification is sent). No output schema exists, and the description offers no insight into the response.

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?

The input schema has 100% coverage with clear descriptions for both parameters (orgId, userId). The description does not add any extra meaning or constraints beyond what the schema already provides, so baseline 3 applies.

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 'Remove a member from the organization' clearly states the verb (remove) and the resource (member from organization), and effectively distinguishes this tool from sibling tools like invite_member, update_member, and list_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?

No guidance is provided on when to use this tool versus alternatives (e.g., revoke_invitation for pending invitations, update_member for changing roles). There are no prerequisites or conditions mentioned for using this tool.

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