Pyth Get Price

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds that the price comes from an on-chain oracle and cautions against settlement use, which provides useful behavioral context beyond 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?

The description is two sentences, front-loaded with the main action. Every sentence serves a purpose: stating the operation and providing usage context. No wasted words.

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?

Given the tool's simplicity (one parameter, read-only), annotations and schema cover the essential details. The description adds the source (on-chain oracle) and usage boundaries (not for settlement). With an output schema present, the description is sufficiently complete.

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 schema already describes the parameter (priceId: hex or symbol). The description does not add new meaning about the parameter beyond what the schema provides, so it meets the baseline but adds no extra clarity.

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 clearly states the tool gets the current price from a Pyth oracle feed. It mentions 'feed discovery' which slightly broadens the purpose, but the primary action is well-defined and distinguishable from sibling tools like pyth_getPriceHistory and pyth_listPriceFeeds.

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?

The description provides explicit guidance: use for oracle price reads and feed discovery, as context for pricing and risk checks, and explicitly warns against using for settlement. It doesn't directly compare with siblings but contextually implies alternative tools for history or listing.

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