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

No annotations are provided, so the description carries the full disclosure burden. It never states that this is a read-only ranked listing, nor describes pagination, ranking basis, or what happens when category matches nothing. For a zero-annotation tool this is a significant gap.

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?

Two terse, front-loaded sentences with no filler; the resource is stated immediately. It is efficient though arguably under-specified rather than verbose.

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 three-parameter listing tool with no output schema and no annotations, the description is too thin. It omits ranking semantics, filtering behavior, return shape, and its relationship to sibling leaderboard tools, so an agent cannot call it confidently.

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 0%, so the description must compensate for all three parameters. It only hints at 'window' via the mismatched '24h' label and says nothing about top_n (count/limit) or category (filtering), leaving two parameters entirely undocumented.

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 phrase '24h volume leaderboard' names the resource (a ranked market list) but no explicit verb, so it reads as a bare noun. It also undersells the tool: the schema's window enum allows 1h and 7d, contradicting the hard-coded '24h' claim. It does not distinguish itself from the close sibling pax.liquidity_leaderboard.

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?

'Useful for surfacing hot markets' implies a use case but gives no explicit when-to-use versus alternatives. With siblings like liquidity_leaderboard, probability_movers, and market_search available, the description never routes the agent to the correct tool or states exclusions.

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