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

Annotations already disclose readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the ranking resource and metrics but does not add operational details such as pagination, rate limits, auth, or result ordering beyond what annotations and schema imply.

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?

A single sentence states the tool's output and two ranking modes with zero filler, and the key information is front-loaded. It is appropriately sized for a simple lookup tool.

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 rich annotations and schema constraints for limit, the description is minimally adequate for this simple leaderboard. However, it omits the limit parameter and does not describe what each ranked wallet entry contains, so it is not fully complete for a tool with no output schema.

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 50%: the 'by' parameter is described in the schema, while 'limit' has no description anywhere. The description repeats the two ranking options already listed in the enum but adds no new syntax, default, or meaning for either parameter, and says nothing about the undocumented limit.

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 ranking operation over a named resource ('Hyperliquid wallets') and two ranking bases, so the purpose is clear. It does not explicitly distinguish itself from nearby ranking/analytics siblings such as open_interest_ranking or cohort_positioning, keeping it short of a 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?

The description gives no when-to-use condition, no exclusions, and names no alternatives among the many sibling analytics tools. The intended use is inferable from the name, but the definition provides no guidance.

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