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

With no annotations at all, the description carries the full burden. It does add value by disclosing the returned fields (liquidity, price, 24h change), which substitutes for the missing output schema, but it never confirms this is a read-only operation, states defaults when parameters are omitted, or mentions result caps/pagination.

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 and the ranking criterion stated before the payload fields. It is efficient, though so terse that some required information is simply absent rather than omitted for brevity.

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?

For a two-parameter, no-annotation, no-output-schema tool, the description covers what comes back but leaves the caller guessing on how many results arrive by default and what min_volume does. Adequate to attempt a call, incomplete for a confident one.

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 for both parameters and does not. The word 'top' loosely hints that a limit exists, but neither the default result count nor the meaning, units, or filtering behavior of min_volume is explained anywhere.

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 the source (Polymarket markets), the selection rule (top ranked by 24h volume), and the payload (liquidity, price, 24h change). That is enough to separate it from generic siblings like trending_markets or kalshi_markets, though it never explicitly contrasts with polymarket_market_scan or polymarket_event_scan.

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 statement of when to use this versus the many market-data siblings (polymarket_market_scan, trending_markets, odds_feed, resolution_history). The agent must infer the routing decision entirely from the phrase 'top... by 24h volume'.

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