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

With no annotations, the description carries the full behavioral burden and adds meaningful context: it states the data comes from Hyperliquid public data, that the numbers are verifiable on the explorer, and defines win rate as closed trades that beat their fees. It stops short of explicitly declaring read-only or side-effect-free behavior and says nothing about auth or rate limits.

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 opening sentence front-loads the resource and the metrics it returns, and the two closing sentences add useful verification and usage context without boilerplate. The metric list is dense but earns its space by previewing the return payload.

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?

No output schema exists, so the description must preview return values, which it does thoroughly by naming the scoreboard metrics and the BTC buy-and-hold benchmark. For a three-parameter read tool this is largely complete, though explicit read-only behavior and clearer distinction from overlapping wallet and portfolio tools would close the remaining gap.

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 all three parameters are already documented in the input schema. The description only indirectly touches on period via 'over the same window' and adds no extra meaning for includeHistory or walletId, so the baseline score of 3 is appropriate.

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 description names a concrete resource, a Hyperliquid wallet scoreboard, and enumerates the metrics it returns: balance, P&L, win rate, fees, volume, worst drop, loss cap, and BTC benchmark. That makes the tool's scope clear, but it does not explicitly contrast itself with sibling tools such as get_hyperliquid_balances or get_portfolio, leaving sibling differentiation implicit.

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?

It gives one usage context, 'review how your trading is going before changing anything,' which implies when to reach for this tool. However, it provides no when-not conditions and names no alternative for overlapping needs such as raw balances, loss-cap configuration, or portfolio review, so the agent must infer the routing decision.

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