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

Annotations already declare readOnly/idempotent, but the description adds real behavioral guarantees: page-stability under concurrent saves ('a version saved meanwhile never shifts a page'), the 100-per-page cap, and an important semantic caveat that 'checksRan means checks ran, not that they passed.' That caveat prevents a likely misinterpretation and is exactly the kind of context annotations cannot carry.

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?

Front-loaded and dense, but the long enumeration of returned fields (versionId, number, latest, message, author, date, file count, readiness, checks, link) is largely redundant given an output schema exists. The final caveat about checksRan is buried at the end but is the highest-value sentence.

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 paginated read tool with a documented output schema, the description covers scope, ordering, page stability, cursor reuse, and a semantic trap. Nothing an agent needs to call it correctly is missing.

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% and the undescribed `limit` parameter is partly compensated by 'up to 100 a page.' The description also reinforces the exclusive cursor semantics of beforeVersion and, importantly, explains that a version number or versionId can be reused as `version` in other read tools — meaning 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 ('List the saved versions of a board') plus ordering ('newest number first') and page size ('up to 100 a page'), which clearly separates it from compare_board_versions and list_board_releases.

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?

Gives the precondition ('a board you can read'), the downstream action ('Pass a versionId or number as `version` to any read tool'), and the pagination recipe ('Page with beforeVersion = nextBeforeVersion'). It stops short of naming when to prefer compare_board_versions or list_board_releases instead, but the intended workflow is clear.

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