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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds one concrete effect — the invite link stops working — but doesn't say whether the record is deleted or merely invalidated, whether re-inviting is possible, or what error surfaces for an already-accepted invite.

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?

Eight words, front-loaded with the action and resource, no filler. The trailing clause is a fragment but carries real information about the effect, so it earns its place;

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 two-parameter destructive mutation with strong annotation coverage and no output schema, the basics are present, but an agent still lacks the id-semantics clarification and the post-condition detail (deleted vs. invalidated, behavior on already-accepted invites) needed to call it confidently.

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?

With only 50% schema coverage, the description must compensate and does not: `id` has no schema description and the text never clarifies whether it is the invite id, user id, or org id — ambiguous in an API where org, key, and account ids all exist. Only `org` (defaulted to first org) is documented, which comes from the schema, not the description.

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?

"Cancel a pending invite" gives a specific verb and resource, and the qualifier "pending" scopes it away from cloud_team_remove (removing an active member) and cloud_team_resend. It falls short of 5 only because it doesn't name the adjacent siblings explicitly.

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 precondition (only un-accepted invites) but doesn't state what to do if the invite was already accepted or how this differs from cloud_team_remove/cloud_team_resend. Usage context is implied rather than spelled out.

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