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

Annotations already declare this as a read-only, open-world operation. The description adds some behavioral context by indicating that smart wallets are ranked by skill and insiders by evidence, but it does not explain ranking mechanics, result ordering, limits, or what the returned wallet entries contain.

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 very short and front-loaded, with no unnecessary wording. However, its fragment-like structure is under-specified rather than efficiently concise.

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, three undocumented parameters, and 0% schema description coverage, the description is too thin to fully prepare an agent to invoke the tool correctly. It should clarify sorting, limits, the scam view, and the shape or meaning of ranked results.

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 0%, so the description should compensate, but it only partially maps the view enum values and omits the 'scam' view entirely. It also does not explain the sort options or the limit parameter, leaving most parameter meaning undocumented outside the raw enum and default values.

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 ranked wallets and distinguishes its main view categories, including smart, insiders, all, and sniper bots. It lacks an explicit verb like 'list' or 'retrieve', but an agent can still infer that it returns a ranked wallet collection rather than a single wallet.

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 gives the available view categories but does not state when to use this tool instead of siblings such as get_wallet. There is no guidance on whether it should be used for discovery, screening, or comparison, and no exclusions are provided.

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