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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety needs no restating. The description goes further by disclosing an authorization conditional ('the public link and pending invitations (owner only)') and by itemizing the returned data surface, which helps an agent gauge payload size and content. It stops short of stating truncation or pagination behavior.

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?

It is one long sentence, but a well-constructed one: the purpose is front-loaded and the enumerated contents are dense with signal rather than filler. A bulleted or clause-separated structure would read better, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly, including the owner-only caveat. The main gap is that a full-board read can be large and no guidance is given on truncation, pagination, or when to prefer a narrower tool.

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 coverage is 67%: cardsPerList and includeCards are already documented in the schema, while boardId has no description at all. The description adds no parameter-level detail (no mention of pagination limits, the 1–500 range, or how includeCards=false changes the payload) beyond what the schema states.

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 opens with a specific verb and resource ('Reads one board in full') and then enumerates exactly what the read encompasses — lists, cards, labels, members, custom fields, rules, templates, saved views, archived cards, public link, invitations. This distinguishes it clearly from list_boards (collection-level) and get_task (single card).

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?

'Like opening it in the app' implies the intended use — retrieving a complete board view rather than a summary — but there is no explicit when-to-use guidance and no named alternative (e.g., overview or list_boards) for lighter-weight needs. Sibling routing is left to inference.

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