Compare many wallets at once

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

Annotations already establish read-only and open-world behavior. The description adds useful behavioral detail: wallet caps, the lower cap when includeHip3=true, sorting by balance, and handling of unified-account and portfolio-margin wallets whose funds sit in spot rather than perps.

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 front-loaded with the core lookup behavior, then follows with limits and account-type handling, then concrete watchlist examples. Every sentence adds practical selection or usage value.

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?

For a three-parameter batch read tool with no output schema, the description covers what is returned, the batch size limits, sorting, and important account-type behavior. This is sufficient for an agent to choose and call it 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 description coverage is 100%, so parameter meanings are already documented. The description reinforces includeHip3's effect on the wallet cap but does not add meaning beyond the schema or explain minBalanceUsd semantics in its own text.

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 states a specific verb and resource: looking up balance, account mode, and open positions for many wallets. It clearly distinguishes this batch operation from sibling wallet-singular tools through the 1,000-wallet limit and watchlist framing.

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 clear usage context with watchlist examples such as finding whales or checking what 50 traders hold. It does not explicitly name alternatives like hydromancer_wallet_overview for single-wallet queries, so it stops short of full when/when-not guidance.

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