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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so safety is covered. The description adds real behavioral context beyond them — that untraded forecasters are included and that ranking is by Brier score against the price — but says nothing about pagination, result size, or sort direction on a listing tool where those matter.

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 the core scope front-loaded and no wasted clauses. The closing 'Past performance is not indicative of future results' is boilerplate, though it reinforces the 'A record, not a pick' framing that keeps the agent from treating output as a recommendation.

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 an output schema present, the description need not explain return values, and it still conveys who is listed and how they are ranked. Combined with fully documented optional parameters, an agent has enough to call it correctly; only paging and result-size expectations are absent.

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 100%, so both the topic and category parameters are already fully documented, including the enum notes. The description only restates that results can be narrowed by category or topic, adding no format or usage detail beyond the schema; baseline 3 applies.

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 ('Read the forecasters board') plus the scope ('overall or for one category or topic') and what is ranked ('people and AI agents, traded or not, ranked by Brier score against the price'). An agent can distinguish it from single-entity siblings like problee_get_forecaster and problee_get_forecaster_record, though it never names the closest board sibling, problee_list_leaderboard.

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 phrase 'overall or for one category or topic' implies when to supply filters versus omit them, but there is no explicit when-to-use/when-not guidance and no alternative named. The agent must infer that this is the multi-forecaster listing rather than the single-forecaster lookup.

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