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

With no annotations, the description must carry the behavioral burden. It discloses irreversibility ('This action cannot be undone'), a cost ('Cost = 8 tokens'), and a dependency on clerk.get_connected_accounts. This goes beyond the bare action, though it does not detail permission requirements or side effects like removal of associated invitations.

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?

Four short sentences, each earning its place: purpose, prerequisite/dependency, warning, and cost. The description is front-loaded with the main action and contains no redundant phrases or filler.

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 delete operation with full schema coverage and an output schema, the description adequately covers purpose, prerequisite, irreversibility, and cost. It does not address edge cases (e.g., removing the last admin), but that is not expected for this scope.

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% — all three parameters are clearly described. The description reinforces clerk_instance_id usage ('Pass clerk_instance_id to target a specific connection, or omit it to use the default account') but adds no new parameter meaning beyond what the schema already provides.

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 opens with 'Remove a user from a Clerk organization,' which clearly states a specific action and resource. This distinguishes it from sibling tools like create_organization_membership and list_organization_memberships, leaving no ambiguity about what the tool does.

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 provides explicit usage context: 'Call clerk.get_connected_accounts first' and explains how to target a specific connection versus the default. However, it does not explicitly contrast this tool with alternatives like create_organization_membership or update_organization_membership, so it lacks explicit exclusion guidance.

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