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

No annotations, so the description carries the full burden. It does disclose the ranking metric (turnover = 24h volume / resting liquidity) and that a round-trip cost is reported, which is useful behavioral context. However, it does not state auth/payment requirements (it's an x402 paid tool), rate limits, or output shape. Adequate but with clear gaps.

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?

Three sentences, front-loaded with the core definition, then the filters, then the sibling-based disambiguation. Every sentence earns its place with zero waste.

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?

Complete enough for a filtered ranking tool: it names the metric, the comparison basis, the filters and the alternative. Missing only the undocumented 'limit' parameter semantics and any note on the paid x402 invocation, which would fully round it out. No output schema exists, so explaining return values isn't required.

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 description coverage is 0%, so the description must compensate. It explains the intent of minVolumeUsd and maxSpreadBps (filters to get only markets worth trading), which adds meaning beyond the bare schema. However, the 'limit' parameter is never mentioned, and all three params are typed as 'string' with no format/unit guidance, so compensation is partial.

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: a Polymarket activity screen that ranks markets by turnover (24h volume / resting liquidity) and reports round-trip cost. It explicitly differentiates itself from the named sibling x402-poly-markets.

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 names the alternative (x402-poly-markets for a plain list) and states the selecting condition: use this when the question is 'where is there real activity I can actually participate in'. Also names minVolumeUsd and maxSpreadBps as filters for 'markets worth trading'.

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