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

With no annotations, the description carries the burden and does well: it declares the operation is public/no key required, that the feed is cached JSON, and it explains the response semantics for the two market flavors (yes/no_multiplier = payout per sat staked, bettable price = 100/multiplier; pari-mutuel shows pool split). What it omits is ordering, staleness of the cache, and pagination behavior.

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 with the resource and its key constraint ('open ... with the offered price only'), then payout semantics, then access model. Dense but every sentence carries information; only the raw feed URL is arguably incidental.

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?

No output schema exists, and the description compensates by explaining exactly what the numeric fields mean, which is the main thing an agent could misread. It falls short only on input semantics and on any hint of result ordering or total counts for a paginated list.

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 only 50% and the description says nothing about limit, offset, category, or market_type. The 'offset' parameter has no schema description at all and the description does not compensate for fields that only the enum or the name hints at. All the descriptive text is about return values, not inputs.

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+resource — 'Open prediction markets with the offered price only' — and scopes the result set to markets that actually have a bettable price. It never names or contrasts with siblings like prediction_markets or market_get, so an agent must infer that 'browse' means listing versus a single-market fetch.

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?

Usage is implied: browsing/discovery, public and key-free, plus a note that the same data is available as a cached JSON feed. There is no explicit "use this when discovering markets before calling market_place_bet

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