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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral fact beyond that: results are returned per board, and an unknown brand name yields no score rather than an error. It says nothing about what the row contains or whether the brand must be pre-reviewed versus merely existing.

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?

Two short sentences with the resource scope front-loaded and the negative-case behavior trailing. No filler, though 'row on each board' is terse to the point of ambiguity about the return shape.

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 lookup tool with one opaque parameter and no output schema, the description leaves the return payload entirely undefined beyond 'row on each board' – an agent cannot tell what fields or how many rows come back. Combined with zero parameter documentation, it is under-specified for correct invocation even allowing for the annotations covering safety.

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% for the single `brand` parameter, so the description must carry the meaning and largely does not. 'Unknown names are not given a score' implies the value must match an existing reviewed brand, but it never mentions the required slug form (lowercase, digits, hyphens), length limit, or case sensitivity enforced by the schema pattern.

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 the resource (one reviewed brand) and the retrieval scope (its row on each board it is scored on), so an agent can tell it fetches per-board brand scoring data. It does not differentiate itself from siblings like get_category_board or get_movers, so the purpose is clear but not sibling-distinguishing.

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 this tool versus get_category_board, get_movers, or get_question. The only conditional sentence ('Unknown names are not given a score') is an outcome/error note, not usage guidance or a prerequisite.

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