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

With no annotations present, the description carries the full behavioral burden and does much of it: cost ($0.01 USDC on Base), payment rail, no account or API key required, sort order, and the returned fields. Missing are rate limits, failure modes, and whether repeat calls are re-billed, which keeps it short of a 5.

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?

Front-loads the payment status and purpose in one dense line, then lists payload, cost, auth, and endpoint. Telegraphic phrasing but no filler; slightly fragmented as a reading flow.

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 zero-required-parameter paid read with no output schema, the description covers purpose, returned fields, price, auth requirements, and endpoint — enough for an agent to decide and call. Only rate/error behavior and sibling routing are absent.

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 coverage is 100% and the single 'limit' parameter (1-50, default 10) is fully documented there. The description adds no syntax or default detail beyond the schema, so the baseline 3 applies.

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 ('Live Polymarket odds for fed markets'), a scoping/sort rule (by 24h volume), and the exact payload fields returned. This clearly separates it from the many buy_coin_* siblings and from the adjacent buy_pm_interest-rates topic.

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?

The leading 'Paid.' plus the price line tells the agent this is a metered call, but there is no explicit guidance on when to pick this over buy_pm_interest-rates or the generic buy_polymarket sibling. Usage is only implied by the topic keyword in 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.