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

With no annotations, the description carries the full behavioral burden, and it does disclose one important trait: a metered cost of 0.001 USDC per call via x402. It does not describe data freshness guarantees beyond 'live'/'recent samples', rate limits, or the payment handshake itself, though the paymentProof schema field covers the 402 flow in detail.

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, metrics front-loaded, cost stated last. Every clause carries information and nothing is padded.

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 should describe return values; it lists which metrics come back but not their units, formats, or response shape (e.g., whether epoch progress is a percentage or fractional). The payment mechanics are covered by the schema, so the remaining gap is moderate rather than severe.

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?

There is a single parameter with 100% schema description coverage, and the schema fully explains the paymentProof flow (omit first, pay, resend with proof). The description adds only the price figure, not additional semantics, so the baseline 3 applies.

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 the specific resource (Solana network metrics) and enumerates the exact data points returned: TPS over recent samples, current slot, block height, and epoch progress. That is enough to distinguish it from sibling tools like gas_price, chain_tvl, or crypto_price, which cover different resources.

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?

There is no statement of when to use this tool versus alternatives such as chain_tvl or gas_price for Solana-related questions, and no exclusions. The only usage-adjacent content is the pricing note, which signals cost but doesn't route the agent.

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