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

With no annotations, the description carries the full burden and does well: it discloses that the call is paid ($0.10 USDC on Base), requires no account or API key, is sorted by 24h volume, and lists the returned fields. It stops short of explaining how the payment is actually settled per call or what happens on payment failure, which an agent needs before invoking a paid 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?

Telegram-style and front-loaded: purpose, then return fields, then price/auth, then endpoint. Every clause carries information; the raw URL is arguably redundant but is genuinely useful for a paid x402-style endpoint.

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?

No output schema exists, so enumerating the returned fields is necessary and it does so. Cost, auth model, sort order, and data shape are all covered; the only real gap is operational payment mechanics and error behavior for a paid call.

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?

Only one parameter (limit) exists and the schema documents it fully at 100% coverage, so the baseline of 3 applies. The description adds the volume-sorting behavior but says nothing about the limit or its default, adding no meaning 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 exactly what is returned: live Polymarket odds for 'oscars' markets, sorted by 24h volume. Combined with the topic-scoped name, an agent can tell this apart from the other buy_pm_* topic tools (f1, nba, election, etc.) without opening the schema.

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 topic scope — an agent infers 'call this when you want Oscars market odds.' The description spends its words on pricing and auth rather than on when this beats buy_polymarket or buy_search, and gives no exclusions or alternatives.

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