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

With no annotations, the description carries the full burden and does so: it discloses cost ($0.002 USDC), the sampling floor (at least 50 txs, paging toward 24h, cap 300), and the degraded-response condition (null rates with windowTooShort=true under an hour of activity). These are exactly the behaviors an agent must anticipate before spending money on the call.

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?

Front-loaded with the value proposition and metrics, and every clause adds real information (cost, edge cases, usage). It is dense and could be split into two sentences for readability, but nothing is redundant.

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?

No output schema or annotations exist, yet the description lists the returned fields, the cost, the lookback/paging behavior, and the null-rate edge case. That is sufficient for an agent to decide and call correctly.

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 100% for the single 'address' parameter (base58 Solana wallet), so the schema already carries parameter meaning. The description adds no additional parameter guidance, which is acceptable at baseline 3 for a fully documented single-param 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?

States a specific verb+resource with its differentiator ('Cheapest Solana wallet screen on x402') and enumerates the exact metrics returned. It explicitly positions itself against the heavier sibling /wallet/profile, so an agent can distinguish the fast screen from the full profile without opening a schema.

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?

Names the intended workflow ('filter copy-trade candidates before buying a full /wallet/profile'), which is both a when-to-use and an explicit alternative. The implied when-not-to-use (when you need the full profile) follows directly from the named sibling.

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