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

Annotations already declare destructiveHint=true and non-idempotent, but the description adds substantial context beyond them: login required, initiator-only authorization, irreversibility, the side effect that the invite vanishes from the recipient's to-do list, and precondition checks before acting.

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?

Dense but front-loaded: authorization and irreversibility come first, then ID sourcing, then the precondition branch. Every clause carries a distinct obligation, though the compact run-on style slightly reduces scannability.

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 no output schema, the description covers the authorization model, the ID source, irreversibility, the precondition case, and the observable effect — everything an agent needs to call it correctly.

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 coverage is 0%, so the schema alone gives no meaning to inviteId. The description compensates by telling the agent where to source it — get_collaboration_goal(include=invites) — which is exactly the missing guidance, though no format/validity detail (e.g. the 40-char bound) is conveyed.

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 states a specific verb and resource — withdrawing a collaboration invitation — and immediately scopes it to 'unresponded invites by the target initiator'. This differentiates it cleanly from siblings like cancel_alliance_invitation and respond_collaboration_invite.

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?

Explicit when-to-use rules: only the initiating party, only for invitations with no response yet, verify the recipient before confirming, and do not retry when the invite is already accepted/declined/expired — instead check current status. Nothing is left to inference.

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