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

Beyond the annotations (destructive, non-idempotent, open-world), the description adds the required permission (MANAGE_USERS), the exact HTTP outcome (204), and the API-key scope (users:write). These are real operational facts an agent needs before invoking a destructive call, though irreversibility/rate-limit details are absent.

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 sentences, front-loaded with the action and its target, followed by permission, result, and scope. No filler; every clause carries information.

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 single-target destructive operation with no output schema, the definition covers what is acted on, the permission prerequisite, and the return code (204, empty body). Nothing an agent needs in order to call this correctly is missing.

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 account, workspace, and invitationIdentifier are already documented in the schema. The description only restates that the identifier selects the invitation; baseline 3 applies since the schema does the heavy lifting.

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 (revoke) and resource (pending workspace invitation) plus the means of selection (by its identifier). This clearly distinguishes it from pm_send_invitation, pm_list_invitations, and the member-management siblings without needing to name them.

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 the tool only applies to invitations not yet accepted, which is useful scoping. However, no alternatives are named (e.g., pm_remove_workspace_member for accepted members) and there is no explicit when-not guidance beyond that implication.

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