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

The description adds meaningful behavioral details beyond the readOnlyHint/destructiveHint annotations: results are ordered largest first, the token is named once for the whole list, and an empty list means no indexed holders on that side rather than an error. These details help the agent interpret responses correctly without an output schema.

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 most important scope and version constraint, and each sentence carries useful information. The reserveId sentence is slightly redundant with the schema, and the token-naming detail could arguably live in an output schema, but the overall length is reasonable and organized.

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 no output schema, the description does well to explain ordering, the single-token naming behavior, and the empty-list error semantics. It does not spell out the exact fields returned per wallet, but this is a relatively simple list tool and the schema plus description cover the essential calling context adequately.

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 the schema already documents all five parameters. The description's only param-related contribution, pointing to get_markets or get_position_items for reserveId, is also already present in the schema description. Thus the description adds little semantic value beyond the input schema.

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: listing the biggest wallets supplying or borrowing a v4 reserve, sorted largest first. It clearly centers on concentration questions, which distinguishes it from the many other get_* siblings. The title and first sentence together make the tool's purpose immediately recognizable.

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 explicitly says to use this tool for concentration questions, such as whether one address holds most of a reserve's liquidity or debt. It also notes the v4-only constraint and tells the agent where to obtain reserveId. It does not name specific alternative tools or exclusion cases, but the usage context is clear.

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