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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the authorization model (inviter or board admin only), which the schema does not. It says nothing about irreversibility, whether the invitee is notified, or what happens to the invitation record after cancellation, leaving meaningful gaps for a mutation tool.

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 action and its scope come first, followed immediately by the permission constraint. Nothing is redundant.

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 no annotations and no output schema, the description covers purpose and the key access constraint. It could still note whether cancellation is reversible or what the caller should expect on success, but the essentials are present.

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 there is a single required parameter, so the schema already fully documents invitation_id. The description adds no syntax, format, or sourcing guidance (e.g., where to obtain the ID from list_pending_invitations), so the 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 board invitation'), which is unambiguous and distinguishable from nearby tools like invite_board_member and respond_to_invitation. It does not, however, explicitly name which sibling to use in adjacent scenarios, so it stops short of full sibling 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?

It gives a real prerequisite — 'Only the original inviter or a board admin can cancel' — which tells the agent who may invoke it. It does not say when to prefer this over respond_to_invitation (invitee declining) or remove_board_member (removing an existing member), so routing guidance is only implied.

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