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

Annotations already declare non-read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds the useful qualifier that only *pending* invitations can be revoked, but says nothing about what happens on an already-accepted invite, whether a re-invite is possible, or notification side effects.

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?

A single short sentence with no filler, and the key qualifier ('pending') is included up front.

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 two-parameter mutation with full annotation coverage, the description is adequate but thin: it does not cover failure modes (unknown/already-used invitation), whether the action is reversible, or any confirmation of scope beyond 'pending'.

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 both parameters are documented in the schema, setting the baseline at 3. The description adds no extra detail on invitationId (e.g., format or where to obtain it) or on the organizationId scoping constraint that the schema flags as 'approved workspace id only'.

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+resource (cancel an invitation) and narrows scope to pending invitations, which distinguishes it from siblings like accept_invitation and invite_member. It does not explicitly name those siblings, but the action is unambiguous.

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 explicit guidance on when to use this vs. alternatives such as remove_member or accept_invitation, and no mention of prerequisites (e.g., invite must be pending). Usage is only implied by the verb.

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