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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is the error behavior: 400 when non-'all' windows are stale beyond 2 days on base/hyperevm. That is a concrete behavioral trait an agent cannot get from structured fields, though pagination and result shape are not covered.

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 tight sentences with purpose front-loaded and the operational caveat second. Minor terseness ('otherwise a 400') but no wasted prose.

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?

With no output schema, the description does not indicate what a result row looks like (wallet address plus which metrics) or how pagination behaves with size. For a discovery/ranking tool, that leaves a noticeable gap even though the window-freshness caveat is covered.

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%, so the schema already documents size, sort, chain, order, window, and include_hubs. The description largely restates the sort metrics and window rule already in the schema; only the '400' consequence adds meaning beyond it.

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 (find top wallets) plus the ranking metrics, so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from nearest siblings such as hl_perp_top_traders or wallet_compare, leaving that inference to the agent.

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 second sentence gives real usage guidance for windows on base/hyperevm and the 400 failure mode, which is useful. But there is no explicit when-to-use-this-vs-alternative guidance, and no mention of when to set include_hubs or when to prefer another wallet tool.

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