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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds one concrete consequence ('its link stops working'), which is genuinely useful, but says nothing about reversibility, error behavior on non-pending invitations, or whether the teammate can be re-invited.

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 clause, front-loaded with the action and its consequence, with zero filler. Nothing could be removed without losing information.

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 one-parameter, non-open-world mutation whose annotations already cover destructiveness, the description is largely sufficient. The only remaining gap is failure/edge behavior (what happens if the invitation is already accepted or expired), which is minor here.

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% and the single parameter already documents its source ('From list_team'), so the baseline is 3. The description adds no meaning about invitationId beyond what the schema provides.

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 a pending invitation') and adds scope ('pending'), which signals this only applies to invitations not yet accepted. It does not explicitly distinguish itself from the closely related siblings resend_invitation or remove_teammate, so it falls 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?

Usage is only implied by the word 'pending' — an agent can infer that accepted invitations cannot be revoked, but the description never states when to revoke versus resend (resend_invitation) or when to remove an existing teammate (remove_teammate). No explicit alternatives or exclusions are given.

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