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

With no annotations at all, the description carries the full burden and does substantial work: it discloses that the call is paid, the exact price and payment chain, that no auth is required, and the sort order (24h volume). It omits failure behavior, rate limits, and freshness/caching of the odds, which are meaningful gaps for a paid data endpoint.

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-loaded with the critical fact ('Paid.'), then the resource, sort order, returned fields, price, auth requirements, and endpoint. Every clause is informative and there is no filler.

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 one-parameter tool with no output schema, the description covers what is returned (odds per outcome, volume, liquidity, end date, link), the cost, the auth model, and the ordering. What's missing is guidance on choosing it over the generic buy_polymarket sibling and any note on data staleness.

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?

The single 'limit' parameter is fully described in the schema (100% coverage, including the 1-50 range and default), so the schema does the work. The description adds nothing about the parameter, which is acceptable at this coverage level but not value-adding.

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 states a specific verb+resource: paid retrieval of live Polymarket odds for 'bitcoin' markets. The topic word 'bitcoin' implicitly separates it from siblings like buy_pm_ethereum and buy_pm_crypto, but the generic buy_polymarket alternative is never named, so differentiation is inferred rather than stated.

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?

It gives useful preconditions ('$0.002 USDC on Base. No account, no API key') that tell an agent this is callable without setup, but it never says when to pick this over buy_polymarket or the broader buy_pm_crypto tool. Usage context is implied by the topic name only.

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