tenero_trending_pools

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful context: read-only inspection implied by 'List', the last-hour time window, the data source (api.tenero.io), and that no authentication is required. It says nothing about rate limits, caching/staleness of the trending data, or pagination behavior beyond the schema's limit.

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 core capability and returned fields are front-loaded in the first two sentences with no waste. The API attribution and the trailing `earning_opportunities` tip are mildly extraneous but short and do not obscure the main point.

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 two-parameter read-only listing tool with full schema coverage and no output schema, the description covers what it does, what it returns, the time window, and the auth posture. The remaining gap is sort order and whether results are cached, which is minor at this complexity.

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%, with both `chain` and `limit` documented including defaults and bounds, so the schema does the heavy lifting. The description adds the 'last hour' time window, which is not expressible in the parameters, but adds nothing about chain semantics or ordering of the returned pools. Baseline 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 and resource with scope: 'List trending DEX liquidity pools by volume over the last hour.' The description also enumerates the returned fields (platform, token pair, volume, liquidity), so the agent knows exactly what it gets. It does not differentiate from pool-listing siblings such as styx_pools, alex_list_pools, or bitflow_get_routes, which keeps it at 4 rather than 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?

There is no guidance on when to choose this over the other pool/quote tools in the sibling set. The only routing hint is a 'Tip' to call `earning_opportunities` afterward, which is a next-step suggestion rather than a condition for selecting or avoiding this tool.

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