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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context: it filters by token, restricts to winning wallets, and computes the best trade per wallet. No contradictory or surprising behavior is disclosed.

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, well-structured sentence with no filler. It front-loads the core question—winning wallets holding the token—and follows with the additional output detail about the best trade. Every part earns its place.

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 one-parameter read-only tool, the description gives enough context: it names the input, the subset of wallets, and the per-wallet output. Minor ambiguity remains around the exact meaning of 'best trade' (e.g., by profit, ROI, or size) and how results are ordered, but nothing critical is missing.

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?

The schema fully documents the single address parameter, including its checksummed Ethereum-style pattern and that it represents a token contract on Robinhood Chain. The description only references 'this token' and adds no further parameter-specific semantics, so baseline 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 states a specific function: identify winning wallets that hold a given token and return each wallet's best ever trade. This distinguishes it from sibling tools like token_holders (all holders) and winners (all winning wallets). The resource and query scope are explicit.

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 makes the use case clear: pass a token address to find winning wallets holding it and their best trade. It does not explicitly name alternatives or exclusions, but the token-specific intersection is strongly implied by the wording, giving clear context without needing further inference.

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