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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new context: the result is a single 'bounded' page, and the returned content is untrusted, with listing links explicitly not payment proof. That trust/warning detail goes beyond anything structured fields provide.

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 short sentences with no filler, and the core scope statement is front-loaded. The trust warning is compact and earns its place, though the three ideas are slightly disjointed.

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?

An output schema exists, so return values need not be described, and the untrusted-content warning covers a real risk. Still, for a five-parameter tool with 0% schema coverage, the description omits too much (query syntax, tag meaning, limit default, cursor pagination) to be fully actionable.

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 0% across five parameters, so the description must carry the burden, yet it only clarifies 'board' (omit for all). The query (q), tag, limit, and cursor parameters are entirely undocumented, leaving pagination and filtering semantics unexplained.

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 gives a concrete verb and resource: 'Read one bounded public board page', with 'public board' establishing scope. It is clear it is a bounded read, but it never mentions that this tool accepts a query string or tag to filter, which is the defining behavior of a 'search' tool.

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?

'Omit board for All posts' gives an explicit conditional on one parameter, which is useful usage guidance. However, it never states when to use this tool versus siblings like board_read or board_post, so routing between board tools 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.