Revoke Workspace Invitation

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

The annotations already declare destructiveHint=true and readOnlyHint=false, which covers the safety profile. The description adds no extra detail about side effects, permissions, or reversibility, but since the annotations carry that information, a baseline score of 3 is appropriate.

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, clear phrase with no unnecessary words or redundancy. It is perfectly sized for a simple tool action and easy to parse quickly.

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?

The description lacks context about the consequence of revocation (e.g., whether it is irreversible, whether it only affects pending invitations, or if it notifies the invitee). Given there is no output schema, this additional context would help the agent understand the full impact of the action.

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?

The schema provides no descriptions for workspaceSlug or invitationId, and the tool description does not clarify their meaning or expected format. With 0% schema coverage, the description should compensate but it is completely silent on parameters, offering no semantic value.

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?

Tautological: description restates name/title.

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 guidance on when to use this tool versus alternatives such as declineInvitation or deleteWorkspaceInvitation (if it existed). The description does not mention scenarios, prerequisites, or typical use cases, leaving the agent to infer the appropriate context.

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