Revoke User's Organization Invitation

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond the annotations: it changes Calendly state and requires confirm=true. It does not, however, state the permanence of the revocation, whether the invitee is notified, or what it returns, so some transparency is still missing.

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?

Two sentences, front-loaded with the action, then the confirm and scope requirements. No filler. The title is repeated as the first sentence, which is slightly redundant, but it is not wasteful.

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, non-idempotent, open-world write tool with no output schema, the description supplies the scope requirement and the confirm gate, which are the two most likely causes of a failed call. It omits return behavior, post-revocation state, and side effects, but the annotations already flag destructiveness and non-idempotency, so the remaining gap is small.

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% — every parameter has a description. The description adds one semantic point the schema does not: 'requires confirm=true for the specific requested action', which explains the confirm flag's condition. The remaining parameters (org_uuid, invitation_uuid, account) are already fully documented in the schema, so baseline 3 is appropriate.

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?

States a specific verb + resource: 'Revoke User's Organization Invitation'. It maps directly to a distinct resource and is distinguishable from siblings like remove_from_organization (a membership) and delete_contact (a different entity). An agent can tell what it does without reading the schema.

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?

There is no when-to-use guidance, no explicit alternative (e.g., 'use this to cancel a pending invitation; use remove_from_organization to revoke an active member'), and no prerequisites beyond the scope line. The scopes hint at required permission but do not tell the agent when to choose this over siblings.

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