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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the interpretive caveat that this is a record rather than a consensus, which is genuinely useful context, but says nothing about latency, coverage gaps for questions without forecasters, or what happens for uncovered questions.

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 only two sentences, but the first sentence is essentially a verbatim restatement of the title, and it spends its length enumerating return fields that the output schema already carries. The closing caveat is short and earns its place; the bulk does 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?

An output schema exists, so describing return values is not required, yet that is where nearly all the description's effort goes. What is actually missing for a one-param read tool with rich annotations is sibling differentiation and usage framing, leaving the definition adequate but with clear gaps.

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 100% and the single 'question' parameter is documented in-schema as a slug or Kellian/Polymarket link. The description adds no format, resolution, or ambiguity guidance beyond that, so the 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?

Specific verb (Read) and resource (a covered question's forecasts) with the content enumerated: per open option, forecaster count, median and middle half beside the price, plus ranked forecasters' latest. It is distinguishable from per-forecaster siblings like problee_get_forecaster and problee_list_forecasters, but the description never names those siblings to make the boundary explicit.

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 when-to-use or when-not-to-use guidance and no alternative tool is named. The only guidance-adjacent sentence, 'A record, not a consensus to follow,' is a framing caveat rather than a routing rule, so an agent must infer the usage context.

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