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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value beyond that with the data source (on-chain), the TVL threshold, ranking metric, daily refresh cadence, and a caveat about predictive value. It does not describe result count/paging behavior, which limits it to a 4.

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?

Three short sentences, front-loaded with the resource and scope, then the ranking rule and refresh cadence, then a caveat. No filler; every clause carries information.

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 single-parameter read-only tool with no output schema, the description supplies the dataset definition, filter, ranking, and freshness, which is most of what an agent needs; only the limit/result-size behavior is left unaddressed.

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 (limit, default 10, max 100) with 0% schema description coverage, and the description never mentions it, so the agent learns nothing about how many rows come back or how to change that. With low coverage the description was expected to compensate and does not.

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?

Specific verb+resource: it returns a Hyperliquid vault leaderboard from on-chain data, and it defines the exact filter (open vaults with >= $100k TVL) and ranking (30-day PnL in USD). No sibling tool covers a leaderboard, so no differentiation is needed.

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?

The description implies when the result is relevant via 'Refreshed daily' and the eligibility criteria, but it never states when to call this versus alternatives (e.g., get_report_card for a single entity) or any exclusions. Usage is inferable rather than stated.

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