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

Annotations already mark this as destructive, non-idempotent, and not read-only, so the safety profile is covered. The description adds meaningful context: only pending invitations are affected, existing users are not deleted, and approval requirements may be configured by administrators with business workflow approvals always applying.

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 two tightly written sentences with the core action and boundary front-loaded. The approval note is compact and relevant, with no wasted wording.

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 one-parameter destructive mutation with annotations and an output schema, the description provides enough behavioral context about scope and approvals. It could be slightly stronger by clarifying the source or lifecycle of the invitationId, but the essential information is present.

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?

There is only one parameter, invitationId, and its name plus the UUID format/pattern make its purpose fairly clear from the schema. However, schema description coverage is 0% and the description does not explain where to obtain the invitation ID or any additional constraints beyond the schema.

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 uses a specific verb and resource: revoke a pending team invitation. It also clarifies the boundary that it does not delete an existing user, which helps distinguish it from user-removal or deletion operations.

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 clearly scopes usage to pending invitations and states a negative boundary: it does not delete existing users. It also notes that business workflow approvals always apply, giving useful context, but it does not explicitly name sibling alternatives such as resend_team_invitation or list_team_invitations.

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