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

Annotations already cover read-only/idempotent/non-destructive, and the description adds genuinely new behavioral context: this is a paid x402 route at $0.01 per call, plus the exact upstream endpoint. It does not mention pagination or response size for large limits.

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 compact fragments with the ranking criterion front-loaded and cost separated at the end. The literal 'GET /x402/polymarket-trending?limit=' string is slightly implementation-flavored but earns its place by hinting at the limit parameter.

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-optional-parameter, read-only list endpoint with no output schema, the essentials are present: what is returned conceptually (top markets with YES prices) and that payment is required. A brief note on how many markets appear or the response shape would close the remaining gap.

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 100%, so both parameters are already documented — including a detailed explanation of the payment proof flow. The description only mirrors the 'limit' concept via the URL template and adds nothing about valid ranges or defaults beyond the schema.

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 resource and ordering: 'Top open Polymarket markets by 24h volume with YES prices.' This is clearly distinguishable in substance from get_polymarket_odds/book/history, though the description never names those siblings to make the routing explicit.

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?

Usage is only implied by the phrase 'Top open ... by 24h volume' — an agent can infer this is the discovery/ranking call rather than a lookup by market id. There is no explicit when-to-use, when-not-to-use, or pointer to get_polymarket_odds or get_polymarket_book as alternatives.

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