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

Annotations already declare openWorld, non-idempotent, non-destructive, but reveal nothing about cost or the payment handshake. The description fills exactly that gap: $0.01 per call, USDC on Solana, and the required two-step x402 retry with `_meta["x402/payment"]` — non-obvious behavior an agent could not infer. Not a 5 because it says nothing about rate limits, failure modes after payment, or whether the charge repeats on retries.

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?

Three sentences, front-loaded with what it does, then cost, then how to transact, then an HTTP fallback. Every clause carries operational weight 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?

For a paid, output-schema-less tool, the invocation path is fully covered — an agent knows the cost, currency, and exact retry protocol. The only gap is the shape of the returned distribution history, which the agent must discover by calling.

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%, so both `ticker` and the optional `price` are already documented. The description adds no semantics beyond the HTTP path template implying ticker placement; the meaning of `price` for yield math is left entirely to 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?

The first sentence gives a specific verb and resource — fetching an ETF's full distribution history — which is unambiguous on its own. It does not, however, distinguish itself from the sibling 'etf_distributions_simulate', leaving the agent to infer the boundary between the real fetch and the simulated variant.

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?

Usage mechanics for payment are spelled out in detail (challenge-then-retry flow), which is genuinely operational guidance. But there is no statement of when to prefer this over 'etf_distributions_simulate' or when a ticker is invalid/unknown, so the alternative-selection guidance is only implied.

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