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

Annotations already declare read-only, open-world, non-destructive behavior. The description adds materially useful context beyond that: polling every five minutes, a per-call price of $0.01 USDC via x402, merge-by-topic ordering, and the exact fields returned. It stops short of describing payment failure behavior or rate limits, so it is strong but not exhaustive.

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 description is front-loaded with purpose, then output shape, then logistics, and every clause carries information. It is a single dense sentence with a long comma-separated list, which is efficient but slightly heavy to parse in one pass.

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?

There is no output schema, so the description must explain return values, and it does: score, velocity, first/last seen, type label, underlying headlines or market numbers, and pump.fun match count. Combined with the polling cadence and pricing model, an agent has enough context to call this correctly.

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 hours, limit, source, and minScore. The description reinforces 'strongest first' and the merged-source behavior but adds no syntax, defaults, or edge-case guidance 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?

The description names a specific verb and resource (lists trending topics) and immediately scopes it to Google Trends and Polymarket. It also distinguishes the merged, cross-source nature from any single-source alternative, so an agent knows exactly what this tool returns.

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 'right now' and the five-minute polling cadence, which tells the agent the data is fresh but not real-time. However, the description never states when to choose this over alternatives (such as recent_launches for pump.fun activity) or when not to use it, leaving routing to inference.

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