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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that: the concrete consequence (the invitation link stops working) and an authorization requirement ('owner or admin') that annotations do not encode. Return format remains unspecified, but for a 2-param tool with no output schema that is minor.

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, each earning its place: the action and effect first, then the permission gate, then the id provenance. Fully front-loaded with no filler.

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 low-complexity 2-param tool with full schema coverage and annotations covering safety, the description supplies the action, effect, authorization, and id source. Nothing critical is missing, though it stops short of distinguishing this from the member-removal siblings.

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 already documented, including the note that invitation_id comes from get_organization. The description largely repeats that schema-provided provenance rather than adding new format, constraint, or failure-mode detail, so the baseline of 3 applies.

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 (cancel), resource (pending invitation) and the concrete effect ('so its link stops working'), which clearly separates it from invite_member (creates) and remove_member (removes an active member). It never names those siblings explicitly, so an agent still has to infer the boundary between revoking a pending invite and removing a member, keeping it short of a 5.

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?

Gives a clear precondition ('Only an owner or an admin can do this') and tells the agent where to source the id. It does not state when to prefer this over remove_member/invite_member, so there is context but no explicit alternatives or exclusions.

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