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

No annotations are provided, so the description carries the full burden. It discloses the membership precondition for the board_id mode, which is useful, but omits read-only confirmation, output/return shape, and pagination behavior for potentially long lists.

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 compact sentences, each covering one mode, with the default (no board_id) front-loaded. No filler or redundancy.

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-optional-param read tool with no annotations and no output schema, the description covers both call modes and the key permission caveat. Return-format details are the only notable omission, and those are minor for a list operation.

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%, so the board_id meaning is already fully documented in the schema, and the baseline is 3. The description reinforces the same optional/omitted semantics, adding no syntax or format detail beyond the schema.

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 — listing pending invitations — and clarifies the two scopes (personal vs per-board) via board_id. It is clearly distinguishable from mutating siblings like respond_to_invitation and cancel_board_invitation, though it never names an alternative explicitly.

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?

Explicitly tells the agent when to omit board_id (view personal invitations) and when to pass it (view a board's invitations). It even states a prerequisite ('must be a member'), but does not route to adjacent tools such as respond_to_invitation when action is needed.

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