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

Annotations already indicate destructiveHint=true, and the description adds a valuable concrete behavioral detail: the invitation link becomes invalid immediately. This goes beyond the generic destructive flag and tells the agent exactly what consequence to expect.

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 short sentences with no filler. The main action is front-loaded, and the immediate effect is stated in the second sentence. Every word earns its place.

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?

This is a simple two-parameter tool with destructive annotations already provided. The description covers the core behavior and consequence. It is complete enough for an agent to invoke correctly, though parameter-level details would make it slightly stronger.

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 0%, and the description does not mention workspaceId or invitationId at all. The parameter names are somewhat self-explanatory, but the description does not compensate for the missing schema documentation by explaining how to obtain or use these identifiers.

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 ('Revoke') and resource ('a pending invitation'), and clarifies the practical consequence ('The invitation link becomes invalid immediately'). This clearly distinguishes it from related invitation/manage-member tools such as invite_member, remove_member, and list_invitations.

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 phrase 'pending invitation' implies the correct context: revoke only invitations that have not yet been used. However, the description does not explicitly say when not to use it, mention accepted invitations, or name any alternative tool as a fallback.

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