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 the payment model ($0.05 USDC on Base), the payee address, that unpaid requests return HTTP 402, that a valid X-PAYMENT makes the same URL return JSON, and that an empty new set yields 304 or recordCount 0. It omits failure/refund semantics and rate limits, keeping 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 endpoint and price, which is good, but the text is repetitive — '$0.05' appears three times and 'not a new SKU' twice — and mixes pricing boilerplate with functional description. Adequately sized but not every sentence earns its place.

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 5-optional-parameter paid fetch tool with no annotations and no output schema, the description covers the payment lifecycle, all four retrieval modes, and pagination termination behavior. Response shape is only loosely implied ('returns JSON'), which is the main 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 the baseline is 3. The description mostly restates what the parameter descriptions already say (pricing per mode, same-door framing) without adding new format or constraint 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 a specific verb and resource: a paid GET that returns CFTC reparations disposition and Commission opinion text. It is clear what the tool fetches, though it never distinguishes itself from the sibling cftc-orders, instead spending words on pricing ('Not a new SKU').

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?

Gives implied usage for each mode — plain GET for newest chunk, ?before for older, ?since for newer than a watermark, ?id for one official text — but this is parameter routing, not tool-selection guidance. There is no statement of when to prefer this over cftc-orders or other CFTC siblings, so usage is implied rather than explicit.

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