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

Annotations already declare read-only and open-world behavior, so the description adds real value by naming the data source (public RPC), the cost ($0.002 USDC per successful call), the payment rails (x402 on Base/Solana/Arc), and that failed calls are not charged. That billing/auth context is exactly the kind of behavior an agent can't infer from structured fields.

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?

Two sentences, both load-bearing: the first fully front-loads the metric inventory, the second covers the commercial terms. No filler or restatement of the tool name.

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 an output schema present and read-only annotations, the description need not explain return shape, and it covers source and pricing well. A small gap remains around staleness/latency of the snapshot and the epoch referenced, which an agent might want before quoting the numbers.

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?

Only one optional parameter (top) with 100% schema description coverage, so the schema already documents the 1–25 range and default of 5. The description alludes to listing top validators by stake, which maps to the parameter, but adds no range, default, or formatting detail beyond the 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 resource (Solana validator snapshot) and enumerates exactly what it returns: active/delinquent counts, total active stake, stake-weighted commission, cluster skip rate, and top validators by stake. This is clearly distinguishable from siblings like crypto_berachain_pol_validators or crypto_jupiter_solana_routing, which cover other chains or other Solana concerns.

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 implies the use case (cluster health / validator stake distribution analysis) via the listed metrics, but it never says when to pick this over a sibling or what prerequisites apply. The only explicit guidance is the payment model, not selection guidance.

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