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

With no annotations, the description carries the full burden and does disclose meaningful behavior: top markets by volume, blended live probabilities, resolution dates, per-market slugs, plus the HTTP endpoint and $0.04 x402 price. It stops short of explaining auth/payment flow or rate limits/pagination, which a paid endpoint would benefit from.

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-loads the purpose in the first sentence and layers detail predictably, ending with an operational HTTP/pricing/docs footer. There is mild redundancy between the first and second sentences ('one call' / 'one-call board'), but overall it is tight.

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 or annotations, the description usefully enumerates what comes back (markets, probabilities, resolution dates, slugs) and gives cost/endpoint/docs. It is nearly complete for a bulk-read tool, lacking only limit/pagination guidance and any note on refresh cadence of 'live' probabilities.

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?

The single required parameter (limit) has 0% schema description coverage and the description never mentions it, so it adds no semantic meaning about how many markets are returned or how limit interacts with the volume-based ranking. The schema provides constraints but no semantics, and the description does not compensate.

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 ('all active world politics markets with live probabilities in one call') and distinguishes by scope from closely named siblings like probability_board_politics-us. It does not explicitly name alternatives, but the 'board'/snapshot framing differentiates it from calendar and movers siblings.

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 bulk read for agents tracking the state of world politics at a glance' implies the intended use case. However, there is no explicit when-to-use vs. when-not guidance, no mention of alternatives for drill-down or delta tracking, and no prerequisites stated.

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