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

Annotations only declare readOnly and openWorld; the description adds substantial undisclosed traits: pay-per-call pricing (0.11 USDC via x402 at a named endpoint), latency ('under a minute'), coverage limits (15-18 major tokens on Base/Ethereum, native ETH only on Ethereum), one-shot rather than streaming, and output shape. That is rich context beyond the annotations.

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?

Purpose, limits and output are front-loaded and earn their space, but the trailing block on ERC-8004 agent identity, Virtuals ACP, payout wallet and token fee is promotional noise relative to invoking the tool. The definition is usable but over-long.

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 steps in to describe the return (priced events in USD, per-chain coverage, HL positions). Combined with cost, latency, coverage limits and an example call, an agent has everything needed to invoke 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%, so the baseline is 3, but the description reinforces semantics with a concrete invocation example and restates the chains/lookback/min_usd dimensions. It doesn't add per-parameter defaults beyond the schema, so it stays short of a 5.

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+resource: large buys, sells, bridges and transfers by one address on three named chains over a bounded lookback, plus Hyperliquid positions and fills. An agent can distinguish what this returns versus a general market scan or smart-money feed without opening the schema.

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 opening 'For traders and agents tracking a wallet' and the 'one-shot check, not a live feed' caveat give usage context and an exclusion. However, no sibling is named and the closely related hl_smart_money and hl_trader_copy_check are not contrasted, so the agent must infer which wallet-tracking tool to pick.

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