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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses pricing ($0.009 USDC / 9000 base units), the x402 payment handshake, that unpaid calls return 402 regardless of query validity, that invalid signed arguments are rejected before settlement, and that stale/cached/cacheAgeMs can be set on a served result. It also notes labeled exchange hot wallets are excluded from clustering, which materially affects interpretation of results.

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?

Purpose is front-loaded correctly and the payment/caching caveats are genuinely needed, but the $0.009 USDC / x402 pricing is stated three separate times (mid-description, the HTTP GET sentence, and the bracketed falcon.sol suffix), which is redundant bulk an agent does not need repeated.

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, the description does the work of explaining the return surface (cluster id, plain-language sybil reasons, cached/stale/cacheAgeMs) plus the full billing and payment flow. It stops short of describing the response shape or what a null/absent funder looks like, which is the main remaining gap for a paid query tool.

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 both address and peers are already documented in the schema, making 3 the baseline. The description adds only marginal meaning, restating that peers compares up to 8 wallets and that peers are folded into the cluster analysis alongside the primary address.

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?

States a specific verb and resource chain: find a wallet's first SOL funder, flag wallets sharing that funder or a CEX deposit address, and return a cluster id with sybil-risk reasons. That is far more specific than siblings like wallet_profile or wallet_quick, but the description never names or contrasts those siblings explicitly, leaving differentiation to inference.

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?

"Use this when you need a wallet's first SOL funder and whether other wallets look like the same operator" gives a clear trigger condition, and the peers note explains when to expand scope. There is no explicit when-not-to-use or named alternative among wallet_quick, wallet_profile, or suggest_peers.

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