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

With no annotations provided, the description carries the full behavioral disclosure burden. It explains that ranking is by total volume, that rows include x402 settlement fields and an unclassified category, and that a high total with zero x402 payments indicates an ordinary transfer flow. This is meaningful caveat disclosure beyond what the schema provides.

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 ranking rule and uses the remaining sentences to clarify the x402 distinction and real-world interpretation. It is slightly longer than strictly necessary but every sentence adds value and the structure is logical.

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 there is no output schema, the description sufficiently describes the key row fields and how to interpret them. It also provides the main use case. Gaps remain around exact limit/sinceDays behavior and the definition of indexed payTo addresses, but the tool is reasonably understandable for an agent.

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 coverage is 0%, so the description must compensate. 'Last N days' strongly implies the sinceDays parameter, and 'wallets that sent the most' implies limit controls how many wallets are returned. However, it never explicitly defines the parameters, their defaults, or valid ranges, leaving room for misinterpretation.

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 names a specific resource and action: wallets sending USDC to indexed payTo addresses, ranked by total USDC volume. It explicitly contrasts itself with x402 settlement ranking, making its scope unambiguous. This clearly separates it from similar sibling tools like mainstreet_top_raters.

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 clear usage context: use it for prospecting and read the x402 columns to distinguish ordinary transfers from customers. It does not explicitly name alternative tools or state when not to use it, but the context is strong enough to guide appropriate selection.

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