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

Annotations already convey that this is a non-read-only (readOnlyHint=false), non-destructive (destructiveHint=false), idempotent (idempotentHint=true) operation. The description adds the 'pending' scope but does not disclose any additional behavioral details such as side effects (e.g., notifying the invitee) or the state change after revocation. With annotations covering the safety profile, the description's contribution is minimal but consistent.

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 a single sentence with no filler words. 'Revoke a pending workspace invitation' is direct, action-first, and fully front-loaded. 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?

For a simple action with only two parameters, a rich schema, and helpful annotations, this description is nearly complete. It lacks an explicit statement about the outcome (e.g., 'the invitation becomes invalid') but the verb 'revoke' conveys that. No output schema exists, so explaining return values is unnecessary.

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%, and the schema clearly explains both parameters: invitation_id is required and sourced from list_workspace_members → pending_invitations; workspace_id is optional with a default. The description itself adds no parameter-specific meaning, so the baseline of 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?

The description 'Revoke a pending workspace invitation' uses a specific verb ('revoke'), a precise resource ('pending workspace invitation'), and includes a qualifier ('pending') that distinguishes it from accepting invitations or removing existing members. This clearly differentiates it from sibling tools like accept_workspace_invitation and remove_workspace_member.

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 word 'pending' implies this tool is for invitations that have not yet been accepted, but the description does not explicitly state when to use it versus accept_workspace_invitation or other alternatives. It also does not mention any exclusions (e.g., what happens if the invitation is already accepted). The parameter hint in the schema about list_workspace_members adds some contextual guidance, but the description itself only implies usage.

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