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

With no annotations, the description carries the full burden and does meaningful work: it discloses membership gating and that unknown-namespace, unknown-board, and non-member all produce indistinguishable errors (anti-enumeration semantics). It omits return shape, required scopes beyond membership, and rate limits, keeping it short of a 5.

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 purpose, then the resolution algorithm, then the failure semantics. No filler and no repetition of schema text.

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 lookup with no output schema and no annotations, the description covers identity resolution, scoping, and error cases adequately. It leaves the returned board shape unspecified, though an agent can reasonably infer it returns the board entity.

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 100%, so the baseline is 3, but the description adds the cross-parameter relationship the schema cannot express: namespace_slug is resolved first, then board_code is looked up within that namespace. That ordering and containment meaning is genuine added value.

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+resource ('Canonical lookup for a board') and explains the exact resolution mechanism: namespace by slug, then board by 3-character code. This is clearly distinguishable from sibling list_boards (plural enumeration) and get_board_settings (settings rather than identity resolution).

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?

The word 'Canonical' implies this is the preferred single-board fetch path, and the error behavior hints at when it will fail, but no sibling is named and no explicit when-to-use/when-not guidance is given. An agent must infer that list_boards is the alternative for browsing.

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