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

Annotations already declare destructiveHint=true, and the description confirms this by stating it is a 'destructive action' and explains the effect (removes the invitation so it can no longer be accepted). This adds context beyond the annotation, but the core safety information is already captured by the annotation. No contradiction, but the description does not introduce substantial new behavioral details beyond confirming the destructive nature.

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?

Two sentences, no fluff. The purpose is stated first, followed by the effect and a caution about timing. Every word earns its place, and it is easy to scan.

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 destructive tool with one parameter and annotations covering destructive behavior, the description covers when to use, what it does, and how to obtain the parameter. No output schema is present, but that is typical for a destructive action, and the description provides sufficient information for an agent to invoke it correctly.

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 description already provides clear meaning for invitation_id (numeric pending team invitation ID) and even suggests a lookup method when given an email. The description itself does not add further parameter semantics, but the schema is fully descriptive with 100% coverage, so the baseline is 3; the extra hint about using list-team-members elevates it to 4.

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 clearly states the tool cancels a pending team invitation, using specific verb (cancel) and resource (team invitation). It distinguishes itself from sibling tools like invite-team-member or remove-team-member by explicitly targeting pending invitations before acceptance. The phrasing is unambiguous and not a tautology.

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?

It explicitly says when to use: when the user wants to cancel a pending invitation before acceptance. It also provides a concrete prerequisite in the parameter description, directing the agent to call list-team-members first when given an email, which prevents misuse and clarifies the workflow.

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