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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real behavioral context: data is computed from the venue's public API, never from screenshots, self-reported PnL or backtests; ranking is gated by a 30% drawdown rule and sorted by Sortino, with failing entries demoted to high_drawdown. It stops short of describing pagination, ordering within flat sections, or error behavior.

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 claim and the section list are front-loaded, but the first sentence runs on across several clauses and the description is a single dense paragraph. Every clause carries information, yet the shape makes it hard to scan quickly for the key gating and ranking rules.

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 aggregator with no output schema, the description covers data provenance, ranking methodology, section taxonomy and a disclaimer, which is most of what an agent needs. Missing pieces are the shape of returned entries (field names, whether security rating is a separate field) and whether unranked sections still carry the rank/sort fields.

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 coverage is 100%, so the baseline is 3, but the description genuinely enriches the section enum by explaining what each list contains (Hyperliquid vaults with quoted AI claims, builder-fill PnL for apps, ForecastBench/Prophet Arena sources for models). The limit parameter's default is only in the schema, which is fine given coverage.

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 (verified performance leaderboard for AI trading agents, bots and vaults) and enumerates exactly what is measured: return vs BTC, max drawdown, Sortino. No sibling tool overlaps with this resource, so ambiguity is low.

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 per-section summaries act as an implicit router (e.g. 'signals… not ranked', 'vaults… of any strategy'), but there is no explicit when-to-use or when-not-to-use instruction such as 'call this for X; use compare_tools instead for Y'. Selecting between sections requires reading the schema default note ('models, signals and usage only when asked').

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