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

With no annotations, the description usefully discloses two things the schema can't: the call costs $0.01 via x402/USDC, and results are limited to open markets (100 max). It omits return shape, whether probabilities are percentages or 0-1 floats, and what happens on payment failure — meaningful gaps for a paid tool.

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 compact sentences with the core payload front-loaded and cost follow-up in a clear parenthetical. 'Exact' is mildly promotional, but nothing is wasted.

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?

There is no output schema and no annotations, so the description must carry behavioral load; it covers what is returned at a high level and the payment model. For a 3-parameter listing tool with an undocumented sort parameter, it stops short of fully arming an agent to call it correctly.

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 33%, so the description should carry more weight than it does. It restates the 'up to 100' cap already encoded as maximum:100 and says nothing about what sort=players/new/closing actually orders by, leaving the highest-impact parameter undocumented in both places.

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?

Names a concrete resource ('open Vatic markets') and the payload ('live, exact crowd probabilities'), with a scope cap ('up to 100'). An agent can tell this is a bulk listing versus the singular live_market sibling, though the distinction is left implicit rather than stated.

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 only implied by the word 'live' — nothing says when to pick this over live_market, trending_markets, market_history, or market_summary, nor whether it is a pre-step to get_market. No exclusions or prerequisites are given beyond the paid-call note.

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