base_trending

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

With no annotations present, the description must carry behavioral disclosure. It usefully adds pay-per-call cost ($0.02 USDC), the 24h volume window, and the DexScreener boost source. However, it does not disclose output format, ordering, limits, or any side effects, leaving the behavior only partially described.

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 very short and front-loads the core purpose. The cost disclosure is relevant and concise. The phrase 'Fresh feed for agents' adds some fluff but is not harmful, so the description remains efficient overall.

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 tool with no output schema and one undocumented optional parameter, the description should provide more operational context. It conveys the general purpose and cost but omits what response fields to expect, how the single parameter affects results, and any behavior around freshness or pagination. This is a meaningful gap for correct invocation and interpretation.

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?

There is one parameter, 'fields', with 0% schema description coverage. The description never mentions the parameter or how to use it, so an agent has no hint of valid values or behavior. The description does nothing to compensate for the schema's lack of documentation.

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 a specific resource ('base DEX pairs'), a metric ('24h volume'), and a data source ('DexScreener boosts'). It is clearly distinct from sibling tools like base_health, base_block, and base_tx, and mirrors the pattern of polygon_trending. The term 'trending' is somewhat nominal rather than a strong verb, but the intent is unambiguous.

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?

There is no guidance on when to use this tool instead of alternatives such as base_tx or base_stables. 'Fresh feed for agents' vaguely implies timely/snapshot data, but it does not explain selection criteria or compare against sibling tools. An agent would have to infer usage from the tool name and description alone.

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