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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is largely covered. The description still earns credit by adding two things not in structured data: the authorization prerequisite ('After authorization') and the concrete effect that the invitation can no longer be accepted.

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, zero filler, trigger condition front-loaded before the effect statement. Nothing could be cut 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 single-parameter mutation with full schema coverage, no output schema, and annotations carrying the destructive profile, the description supplies everything an agent needs: trigger, precondition, target, and consequence.

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 schema itself already tells the agent to use list-team-members first when given an email. The description only repeats that invitation_id is the target of the cancellation, adding no new format, range, or resolution guidance beyond the schema — baseline 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 and resource ('cancel a pending team invitation') plus a temporal qualifier ('before it is accepted') that separates it from removing an existing member. It does not name the sibling alternatives (remove-team-member, invite-team-member) that would let an agent route without inference.

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?

Opens with an explicit trigger: 'Use this when the user wants to cancel a pending team invitation before it is accepted.' The pending-only condition implicitly excludes already-accepted members, but the description never states the negative case or points to the tool for accepted members.

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