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

No annotations, so the description carries the full burden; it does add real value with 'live', 'ranked by volume', the nested-markets return shape, and a cost hint ('cheapest entry point'). However it says nothing about pagination, response size, or x402 payment/auth requirements, so behavioral coverage is partial.

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 tight sentences with the purpose front-loaded and the routing advice second. The only waste is the leading 'x402-polymarket-scan:' prefix, which merely restates the name.

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?

Describes the return shape in prose (events with their markets) and the cost positioning, which is useful given there is no output schema. But with no annotations and two entirely undocumented parameters, an agent still lacks enough to invoke 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 0% and the description never mentions limit or minVolume. 'Ranked by volume' hints at the existence of a volume filter but does not explain the minVolume format, or why limit is typed as a string, so the description does not compensate for the schema gap.

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 (Scan) plus resource (live Polymarket events ranked by volume), and it explicitly describes what each item contains (its markets inside) and how that differs from a single-question lookup. An agent can distinguish it from x402-polymarket-odds without opening either schema.

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?

Explicitly positions the tool as the entry point ('cheapest entry point in this family'), tells the agent to scan first and then route to x402-polymarket-odds for the chosen market. The when-to-use and the alternative are both named.

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