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

No annotations are provided, so the description carries the full disclosure burden, and it discloses little: 'signed' hints at an authentication or signing requirement but is never explained, and there is no statement about read-only nature, freshness guarantees beyond embedded phrases ('today's', 'last 30 days'), or result shape. For a tool with zero annotation coverage this is a meaningful gap.

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?

Everything in the description earns its place — no filler — but it is a single run-on sentence built from nested parentheses, which makes the value-to-content mapping harder to scan than a short list would be. The resource is front-loaded, though the verb is not.

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 and no annotations, the description does cover the breadth of content per board, which is the main thing an agent needs to choose a value. It still leaves out what 'signed' means for invocation, whether results are live or cached, and any guidance relative to the ten sibling tools.

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%, but the sole parameter is an enum whose five values are each given concrete content and scope: khural is member-by-member and summarised, auctions is lot-by-lot, auction_results covers the last 30 days, rail is today's departures from Ulaanbaatar, and fuel_stations is pump prices by station. This is real meaning added beyond a bare enum list; only the 'signed' aspect of the input remains 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 enumerates the five board types and what each contains, so the resource is identifiable, but the leading phrase 'A signed board:' never states what the tool actually does — fetch, render, or aggregate — and 'signed' is left unexplained. It also doesn't distinguish itself from data-oriented siblings like get_panel, get_family, or get_series.

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 statement of when to use get_board versus the many sibling retrieval tools (get_panel, get_series, get_bulk, get_family). The only implicit guidance is the sub-topic labels themselves, which describe contents rather than selection conditions.

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