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 says nothing about side effects of accepting (joining the board), whether a rejection is permanent, whether permissions or membership are required, or whether an expired/already-answered invitation errors — all material 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?

A single, front-loaded sentence with no filler beyond the perfunctory "Use this command to" opener. It is efficiently sized, though its brevity reflects under-specification rather than tight information density.

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 two-parameter mutation tool with no annotations, no output schema, and no sibling routing, the description is too thin: an agent cannot tell what happens after acceptance, what errors to expect, or how to obtain a valid invitation_id. The schema covers parameters, but the behavioral gap remains.

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%: the schema already explains that accept=true means accept and false means reject, and that invitation_id is the invitation to respond to. The description repeats "accept or reject ... by its ID" without adding format, range, or validation semantics, 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?

The description states a specific verb pair (accept or reject) and a specific resource (a pending board invitation) keyed by ID, which is enough to distinguish it from invite_board_member, cancel_board_invitation, and list_pending_invitations. It does not explicitly name any sibling or state a boundary against them, so it falls just short of the top score.

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?

"Use this command to..." frames the situation (a pending invitation awaiting response), which implies usage, but there is no explicit when-not guidance, no mention that the invitation must exist/be pending, and no pointer to list_pending_invitations as the way to discover valid IDs.

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