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

The annotations already cover the safety profile (readOnly, openWorld), and the description goes meaningfully beyond them by disclosing the x402 USDC-on-Base payment model and, crucially, that a missing payment produces a payment challenge in the response rather than an error. It does not mention freshness, caching, or rate behavior, 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?

Two sentences, zero filler, with the primary capability front-loaded ahead of the payment caveat. Nothing could be removed without losing real information.

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 single-parameter, output-schema-backed tool with readOnly/openWorld annotations, this covers what an agent needs: the return content, the format, and the non-obvious payment/failure behavior. Only minor operational details (data freshness, update cadence) 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 description coverage is 100% — the single 'limit' parameter and its default of 15 are fully documented in the schema, and the description adds nothing about it. Baseline 3 applies when the schema carries the parameter meaning.

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 exactly what the tool returns — the latest crypto news headlines — and adds the delivery format ('clean JSON'). No sibling tool (btc_stats, market_pulse, macro, etc.) covers news, so there is no ambiguity to resolve.

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 implied by the resource name rather than stated: there is no explicit 'use this when...' guidance, though the absence of a competing news sibling makes the choice obvious. The pay-per-call note gives some operational context for deciding whether to invoke it.

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