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

Annotations already cover the read-only and open-world profile, but the description adds material context the annotations cannot: the x402 payment model, the exact cost ($0.002 USDC per successful call), accepted chains, and that failed calls are free. It also discloses latency characteristics via 'publish time and age in seconds'. That is real behavioral value beyond 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?

The main sentence front-loads the resource and the returned fields before moving to mode and pricing; two short follow-up sentences handle discovery and cost. The field enumeration is long, verging on a data dump, but every item is genuinely selectable information for an agent choosing this tool.

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, the description does not need to explain return structure, yet it still names the key fields — mild redundancy rather than a gap. Payment terms, symbol universe, and the list mode are all covered; only relative guidance against competing oracle tools is absent.

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 baseline is 3; the description earns above that by characterizing the symbol universe concretely (BTCUSD, ETHUSD, SOLUSD, XAUUSD, stablecoins, LST rates, ~65 feeds) and restating the 1–20 limit and the list mode, which helps the agent construct valid values.

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 gives a specific verb and resource — reads Pyth oracle prices on-chain from Solana push feeds — and enumerates the returned fields (price, confidence, EMA, publish time, feed id). It does not explicitly differentiate itself from siblings like crypto_chainlink_price_feeds or finance_dia_crypto_oracle, but the Pyth-specific framing makes its niche clear.

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?

It provides one concrete usage instruction — 'Call with list=true for every available symbol' — which is useful discovery guidance. However, there is no guidance on when to choose Pyth over the competing oracle tools (Chainlink, DIA) in the sibling set, and no exclusions or prerequisites stated beyond the payment note.

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