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 the useful constraint that the invite must be unused and unexpired, but says nothing about who may revoke, what state the invite lands in, or how failures surface.

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 front-loaded sentence with zero filler; the verb and resource come first and the temporal qualifier earns its place as real scope.

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?

Destructive semantics and return shape are handled by annotations and the output schema, so the main gaps are authorization requirements and failure behavior (already-used or expired invites). For a destructive mutation with a partially documented schema, it is adequate but leaves real questions unanswered.

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 50%: idempotency_key is fully documented in the schema, while invite_id has only a UUID format/pattern. The description contributes no parameter-level meaning, but invite_id is largely self-evident from its name and format, 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+resource ('Cancel an invitation') scoped to 'one of your groups,' which clearly separates it from list_invites and create_invite. It does not name respond_invite, the tool that actually consumes an invite, so sibling differentiation is implied rather than explicit.

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 clause 'before it is used or expires' gives an implicit precondition, but there is no explicit guidance on when to choose this over respond_invite or create_invite, nor any statement of required role/permission. Usage is inferable but not routed.

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