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

With no annotations, the description carries the full burden. It does disclose two useful traits: only 'active' markets are returned, and volume24hr is the default ranking. It says nothing about pagination, result size limits, refresh/rate behavior, or whether the ranking is live.

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 dense sentence with the core purpose and the default ranking front-loaded. No filler, though the trailing enumeration of return fields is slightly list-like and the phrasing 'or all-time volume' is a touch compressed.

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 no output schema and no annotations, the description usefully enumerates returned fields (prices, bid/ask, spread, price changes, volume, liquidity) and the default sort. Missing only limit/pagination behavior, which is minor for a two-parameter read tool.

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 does explain the 'by' dimension in plain language matching the enum values (24h volume, liquidity, all-time volume) and flags the default. It entirely omits the 'limit' parameter and its 1-50 range, leaving one of two parameters undocumented.

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 specific resource (active Polymarket markets) and the ranking dimensions (24h volume default, liquidity, all-time volume), plus the data returned. An agent immediately knows this is a ranked market listing. It does not, however, differentiate itself from the sibling biggest_movers, which also ranks 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?

No explicit when-to-use or when-not-to-use guidance. The default sort is stated, but nothing tells the agent when to pick this over biggest_movers, search_markets, or market_snapshot. Usage must be inferred from the name and description.

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