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

The description goes well beyond the annotations (which only cover read-only, open-world, idempotent, non-destructive). It discloses the payment model (0.015 USDC on Base via x402), that the calling agent's own wallet pays and the server never holds a wallet, that each source is independently optional so a failing upstream degrades gracefully, and the dedup/ranking behavior (cross_source flag, rank-based combined_score). This is rich operational context an agent needs to invoke it correctly.

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 key facts: paid cost, merged feed, and source list come first. It is somewhat dense and repeats the payment amount twice ('0.015 USDC on Base' and '$0.015 USDC on Base'), which is minor redundancy, but every sentence otherwise 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?

Given a 3-parameter tool with no output schema and annotations that only cover safety, the description supplies the missing context: payment flow, degradation behavior, dedup semantics, and the trade-off vs. wiki_trends_pulse. Nothing an agent needs to call it correctly appears to be missing.

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 schema already documents limit, sources, and payment_header in detail. The description adds only marginal parameter meaning beyond the schema (e.g., reiterating that payment_header is omitted on the first call), so the baseline of 3 is appropriate.

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+resource ('merged trending-topics feed') and enumerates the exact four sources (Hacker News, Lobsters, Mastodon, Wikipedia). It also explicitly differentiates from the sibling wiki_trends_pulse, noting it is 'cheaper and broader.' An agent can distinguish this from wiki_trends_pulse and social_trends_pulse_preview 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?

Provides a specific call pattern: 'Call with no payment_header first to receive the payment requirements,' then call again with the same business arguments plus the signed header. It also names wiki_trends_pulse as the narrower alternative. It lacks explicit when-not-to-use guidance (e.g., when to prefer a paid, non-preview tool vs. the preview sibling).

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