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

With no annotations present, the description carries the full burden and does so well: it discloses freshness ('Fresh every 15 minutes'), trust-tier semantics distinguishing primary official sources from aggregated headlines, and the exact payment behavior ('$0.005 USDC on Base', challenge returned automatically, x402-capable clients retry). Cost, auth flow, and data provenance are all surfaced.

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 what the tool returns, then filters, then freshness, then payment mechanics — a sensible ordering with no filler. It is dense but slightly overloaded for a single paragraph, with the return-field enumeration competing with the payment instructions.

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 the description's enumeration of returned fields (source, publisher, timestamp, original link, trust tier) is doing necessary work, and the payment/freshness context covers the rest of the invocation envelope. Minor gaps remain on error handling beyond the payment retry path and any pagination behavior for limit.

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 three parameters (limit, symbol, category) are already documented with examples and bounds. The description only restates the filter dimensions ('symbol, category, and count') without adding syntax or defaults, so the baseline 3 is correct.

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 precise resource with scope: 'Verified market-moving events for crypto agents' and enumerates the payload fields (headlines categorized, tagged to BTC/ETH, source, publisher, timestamp, link, trust tier). The verb is implicit (returns events) rather than explicit, and no sibling tool (bsc_alerts, market_state, ping) is named for contrast, so it stops short of a 5.

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 through 'Filter by symbol, category, and count,' which tells the agent the levers it can pull, but there is no explicit statement of when to reach for this tool over market_state or bsc_alerts. The x402 payment note gives operational context for invocation but not selection guidance.

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