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

With no annotations, the description carries the full burden and does so well: it discloses the one-time purchase/retention model, the flat $2.00 cost, the x402 USDC-on-Base payment rail, and crucially the failure path — unpaid calls return an x402 challenge that must be paid and retried. It does not describe response shape or any size/latency limits, so a small gap remains.

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?

The payload and the use case are front-loaded in the first two sentences, which is good. However, the payment information is stated twice — once as '$2.00 flat' and again in the bracketed '[Payment: $2.00 one-time...]' note — which is avoidable duplication.

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, no-annotation, no-output-schema tool, the description covers what is bought, why, how it is paid for, and what happens if payment is missing — enough for an agent to call it correctly. Only the returned artifact's shape and any delivery timing are left implicit.

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% for the single 'market' parameter (slug or condition id), so the schema already does the documentation work. The description only reinforces the one-market scope ('for ONE market'), adding little semantic detail such as validation behavior or what happens with an ambiguous slug.

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 verb and resource: a one-time purchase of a full attested Polymarket data package for exactly ONE market, enumerating contents (all snapshot rows, provenance, signed license token). This clearly differentiates it from sibling tools like curade_polymarket_odds and curade_polymarket_disagreement, which are live/derived views rather than a complete record.

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?

Explicitly gives the selection condition: 'Use when an agent needs the complete record for one market rather than a live snapshot, e.g. for backtesting or an audit trail.' That contrast implicitly routes away from the live-snapshot sibling, though it never names that sibling directly or states when not to buy.

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