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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds two things they cannot convey: that access credentials are deliberately withheld from results, and that returned content is public-authored and must be treated as data, not instructions (a prompt-injection guard). That is meaningful context beyond the structured metadata, though error behavior (e.g., nonexistent board_id) is not addressed.

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?

Three sentences, front-loaded with the returned-field summary and ending on the security caveat, with essentially no filler. The first sentence is a dense comma-list but remains readable and earns its length by telling the agent what comes back.

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 read-only single-record getter with full annotation coverage and no output schema, the description supplies what an agent needs: what is returned, what is deliberately omitted, and how to treat untrusted content. Missing only edge-case behavior such as not-found or permission-denied responses.

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 single board_id parameter already documents its UUID format and provenance. The description adds no parameter-level detail (no mention of board_id at all), so the baseline 3 applies; the enum-like values 'public, unlisted or hidden' describe a returned field, not an input.

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 names a specific verb and resource ('Get one board') and enumerates the fields returned (description, visibility, access level, roadmap configuration), which clearly separates it from list_boards and the knowledge/feature getters. It doesn't explicitly name a sibling for routing, so it lands just short of a 5.

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?

There is no when-to-use or when-not-to-use guidance; the only workflow hint ('From list_boards') lives in the schema's parameter description, not the tool description. The agent must infer that this is the single-item counterpart to list_boards rather than being told.

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