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

Annotations already declare readOnlyHint and openWorldHint, and the description goes well beyond them: it discloses the 1.1 USDC x402 payment on Base, the public Hyperliquid data source capped at 10,000 recent fills, expected latency, and a non-advice disclaimer. It does not say what happens for addresses with no or sparse fills, so failure behavior is left uncovered.

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 metrics list and input example are front-loaded and efficient, but the tail is heavily padded with promotional material: a 10% fee diversion to the GHOST77 token contract, an ERC-8004 agent ID, Virtuals ACP links, and payout-wallet matching. None of that helps an agent decide or invoke the tool, and it roughly doubles the description length.

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 carries the full burden of describing return values, and it does so by enumerating every reported metric including a composite score. Combined with the disclosed data source, fill cap, cost, and latency, an agent has everything needed to call this correctly.

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% for the single required address parameter, so the baseline is already high; the inline example {"address":"0x..."} adds a concrete call shape and reinforces that exactly one address (not a list) is accepted. No further semantics (e.g., case sensitivity, chain scope) are added beyond the schema pattern.

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 opening question plus the enumerated output set (account value, PnL net of fees, win rate, drawdown, 0-100 copy-ability score) makes the verb and resource unmistakable: a per-trader copy-trading evaluation on Hyperliquid. It is implicitly distinct from hl_smart_money and hl_quick_trade_idea, but never names or contrasts with those siblings, so an agent must infer the boundary.

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?

Usage is only implied by the framing question and the input example; there is no explicit statement of when to prefer this over hl_smart_money, position_health_check, or hl_quick_trade_idea, and no indication of when it is inappropriate (e.g., a fresh address with no fill history). The 'seconds' latency hint and the 10,000-fill cap are useful context but are not routing guidance.

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