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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds one genuinely useful behavioral fact — the caller must be a board member to use the board_id mode — but says nothing about whose invitations are returned in each mode (sent vs received) or result ordering/limits.

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, zero filler, and the no-argument case is front-loaded before the filtered case. Every clause carries information an agent needs.

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-parameter read tool with full annotation coverage and no output schema, the description is nearly sufficient. The only real gap is clarification of what an 'invitation' is here (incoming to the caller vs. sent by them), which affects interpretation of results.

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 the schema already explains that board_id is an optional filter with the same omitted-behavior semantics. The description restates this almost verbatim, adding only the membership constraint, 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 (list pending invitations) and splits behavior into two clearly-scoped modes based on board_id. It is distinguishable from write-side siblings like invite_board_member or respond_to_invitation, though it never names them 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 says when to omit board_id (your own invitations) versus when to supply it (board-level invitations), and adds the membership prerequisite. It stops short of naming alternatives such as respond_to_invitation for acting on the results.

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