Remove User from Organization

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: that it 'Changes Calendly state' and requires the organizations:write scope, which tells the agent about authorization needs and the confirmation gate.

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?

Three short, front-loaded sentences with no filler; the confirmation and scope constraints come early. The opening sentence does slightly restate the title, preventing a 5.

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 write tool with no output schema, the description covers the key agent-facing facts: state change, confirmation requirement, and required scope. It omits downstream effects (e.g., what happens to the user's owned resources or reversibility), but the annotations carry the destructive warning.

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 description coverage is 100%, so all three parameters (account, confirm, membership_uuid) are already documented in the schema. The description only echoes the confirm requirement and adds no syntax or format detail, matching the baseline of 3.

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 states a specific verb and resource ('Remove User from Organization'), so the operation itself is unambiguous. It does not differentiate from near-neighbors such as revoke_organization_invitation or get_organization_membership, so it falls short of a 5.

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?

It states a prerequisite ('requires confirm=true') but gives no guidance on when to use this tool versus alternatives like revoke_organization_invitation or deleting a contact. No when-not conditions or context of use are offered.

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