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

No annotations exist, so the description carries the full behavioral burden. It does disclose what data comes back ('current prices, liquidity, and volume data'), which is genuinely useful given there is no output schema, but it says nothing about data freshness/caching, pagination, sorting guarantees, or read-only semantics beyond implication.

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?

A single front-loaded sentence with no filler; the core ranking criterion is stated first. It is efficient but so terse that the size itself is a constraint rather than an asset — the space saved is spent nowhere useful.

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 two entirely undocumented parameters, no annotations, and no output schema, the description should at minimum define the category vocabulary and limit behavior. Return fields are covered, but an agent cannot confidently construct a category-filtered call from this definition.

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% for both parameters. The description does not explain what 'limit' bounds (max 100 is only in the schema's constraints, not stated) nor what values 'category' accepts or how it filters the Polymarket universe. The mention of '24h volume' does not map to any parameter.

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?

The description names a specific resource (Polymarket markets) and a specific ordering criterion (top trending by 24h volume), plus the fields returned. It does not distinguish this from the very similar siblings polymarket_market_scan, polymarket_event_scan, or kalshi_markets, leaving the agent to guess which scan to call.

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?

There is no when-to-use guidance and no mention of alternatives, despite several adjacent market-scanning tools in the sibling list. The term 'trending' is not operationally defined (e.g., vs. a volume-ranked scan or an arbitrage scan), so a routing decision cannot be made from the text alone.

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