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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real value by confirming the data is public and free (no auth/key needed) and by enumerating the returned fields in place of a missing output schema. It omits freshness/latency and rate-limit behavior, keeping it short of a 5.

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?

One dense sentence, front-loaded with the core verb and resource, followed by the field list and the access note. Nothing is padded or redundant.

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 field enumeration is the critical completeness piece and it is present, along with the public/free access note. Minor omissions like data freshness or perp-only scope against spot are not spelled out, but an agent can call it correctly from what is given.

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?

There is a single parameter with 100% schema description coverage ('Hyperliquid wallet address 0x... (40 hex)'), so the schema carries the detail. The description only broadens applicability with 'any wallet', adding no further syntax or constraint beyond the schema — the baseline 3 for high-coverage schemas.

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 and resource ('Live Hyperliquid perp account snapshot for any wallet') and enumerates exactly what the snapshot contains (account value, positions, margin, withdrawable). It is implicitly distinct from get_wallet_trades and start_wallet_alerts, though it never names those siblings to route the agent explicitly.

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: 'Live ... snapshot' suggests real-time position lookup versus historical trades in the sibling tool, but there is no explicit when-to-use, when-not-to-use, or alternative-naming sentence. 'Public data, free' weakly signals no authentication is required.

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