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

Annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds meaningful behavioral context beyond annotations by disclosing the $0.01 per-call cost, the x402 USDC-on-Base payment mechanism, and that failed calls are not charged. It does not contradict 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?

The description is a single dense sentence that front-loads the report contents and then covers billing. It is efficient and avoids repetition, though the long list of features makes it slightly dense rather than perfectly scannable.

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?

Given the absence of an output schema, the description compensates by clearly listing the report's return contents, including positions, risk, PnL, volume, spot balances, and 24-hour trading. It also includes cost and billing behavior, leaving little ambiguity about what the agent will receive or pay.

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 address parameter, and the schema itself specifies the expected 0x-prefixed 40-hex-character format. The description does not add any additional meaning or validation detail beyond the schema, 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 clearly identifies the resource as an enriched Hyperliquid wallet report and enumerates the core contents: positions, risk, account value, PnL, volume, spot balances, and recent trading. That is far more specific than a tautology, but it does not explicitly compare itself with sibling tools such as derivatives, liquidations, or coin_snapshot.

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 explains what the tool returns and its cost, but gives no guidance on when to choose it over alternatives. There are no exclusions, prerequisites, or named sibling alternatives, leaving the agent to infer usage from the tool name and report contents.

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