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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds useful authorization context (only the original inviter or a board admin), but says nothing about irreversibility, what happens to the invitee, or error behaviour when the caller lacks permission.

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 short sentences with zero filler, the core action front-loaded and the permission caveat immediately after. Nothing to trim.

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 mutation with rich annotations and a fully described schema, the definition covers the action and the permission gate. A note on irreversibility or on where to get invitation_id would make it fully self-sufficient, but nothing essential is missing.

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 a single parameter with 100% schema description coverage ('Invitation ID to cancel'), so the schema carries the semantics. The description adds no format, sourcing, or lookup guidance (e.g. obtainable via list_pending_invitations), which is the baseline-3 outcome for high coverage.

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 board invitation'), with 'pending' narrowing the scope so an agent won't confuse it with revoking a membership or responding to an invitation. It does not explicitly name the neighbouring alternatives, but the action is unambiguous.

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 description gives a clear trigger condition (a pending invitation exists and should be withdrawn) and an authorization constraint. However, it never contrasts with siblings such as respond_to_invitation or remove_board_member, so the agent must infer which tool applies.

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