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

Annotations already disclose the safety profile (destructiveHint=true, idempotentHint=true, readOnlyHint=false), so the description need not repeat it. It adds the qualifying state 'pending', but says nothing about whether accepted invitations fail or are refused, whether the cancel is soft or permanent, or what permissions are needed.

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 the action and the eligible state, and 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 delete tool whose annotations carry the destructive/idempotent profile, this is minimally adequate. It omits the failure mode for already-accepted invitations and any hint of the result, but with no output schema and full param coverage the gap is modest.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents invitation_id fully. The description adds no format, range, or lookup guidance beyond that, which is the baseline 3 case.

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 gives a specific verb (cancel) and resource (pending invitation), so an agent immediately knows this removes an invitation rather than creating or updating one. It does not explicitly name a sibling such as create-invitation-tool, so it stops short of full differentiation.

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?

'Pending' implies the eligible state for cancellation, which is a meaningful usage constraint the agent can infer. However, there is no explicit when-to-use guidance and no mention of alternatives or what to do for non-pending invitations.

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