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

Beyond the readOnly/openWorld/idempotent annotations it discloses the paid-call mechanics: $0.001 USDC per call via x402, an unpaid call returns the PaymentRequired object and must be retried with params._meta["x402/payment"]. It also describes exactly what an omitted-chain call returns (median, spread, per-feed age, round id, raw eth_call), which is behavior an agent cannot infer from annotations.

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?

One dense front-loaded paragraph that leads with what is priced and on which chains before moving to return shape and payment. The x402 retry sentence is long but is genuinely operational, not padding.

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?

There is no output schema, so the description carries the return-value burden and does so: median, cross-chain spread, per-feed age in seconds, round id, and the exact eth_call. Combined with the payment flow and error path, an agent has everything needed to call and interpret it.

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% and both parameters already carry descriptions, so the baseline applies. The description restates the omit-chain aggregation behavior and the USD-only quote constraint that the schema already encodes, adding little new parameter-level meaning.

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 (read with latestRoundData()) and resource (Chainlink aggregator price) plus the exact asset list and six supported chains. It explicitly disclaims being a DEX quote, which is the most likely confusion in a toolset full of token/price helpers.

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?

Gives a concrete usage rule: omit chain to read every chain with the pair and get median/spread/age. It also sets a boundary versus DEX quotes. It does not name a specific alternative tool in this server, but no sibling is a competing price oracle, so the routing guidance is effectively complete.

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