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

Adds substantial context beyond the readOnly/openWorld annotations: the staleness model (last update time, age in seconds, stale flag), the oracle-contract source, error/no-charge behavior for unknown pairs, and x402 payment. With no output schema, this is the only place an agent learns what comes back.

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?

Four front-loaded sentences: source and scope first, then usage, then failure/billing. Dense but every clause carries information; only the parenthetical about DeFi protocols is borderline 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?

Covers source, scope, return fields, staleness semantics, failure modes, and pricing model for a single-parameter read tool. Nothing an agent needs in order to call it or interpret results correctly is missing.

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 the pair parameter already documents the omit-for-all behavior with examples. The description's 'one pair or all at once' restates the schema rather than adding syntax or normalization rules.

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 (current USD prices), the exact source (Chainlink Data Feeds on Base mainnet), and enumerates every supported pair. An agent can distinguish it from siblings like read_feed or list_prices without opening the 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 concrete use cases (valuing balances, converting USDC amounts, checking a stablecoin peg) and routes billing questions to list_prices. It lacks an explicit when-not condition or a named alternative price tool, so it stops short of full 5-level routing guidance.

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