get_pyth_price

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

With no annotations provided, the description carries the full behavioral disclosure burden. It discloses the data source (Indigo analytics API), that the price is the latest signed Pyth update, and that it is only valid on-chain until validUntil. It stops short of stating read-only guarantees or error behavior, but this is adequate for a simple getter.

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 with no waste: the first sentence states the core purpose, and the second adds meaningful context about the signed payload and validity. Every clause earns its place.

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 single-parameter read tool with an enum schema and no output schema, the description gives enough high-level information to invoke the tool and interpret the result: current price, feed configuration, source, and on-chain validity. It does not enumerate exact response fields, but the context is sufficient for a straightforward getter.

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 description coverage is 0%, but the enum in the schema already enumerates the allowed asset values. The description adds that these are iAssets and that the price is a Pyth price, which helps interpret the parameter, though it does not specify units or output format.

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 identifies the tool's function with a specific verb and resource: it retrieves the current Pyth price for an iAsset plus on-chain feed configuration. This distinguishes it from sibling price tools like get_asset_price or get_oracle_price by emphasizing the Pyth-signed update and on-chain relevance.

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 clear usage context: this returns the exact signed Pyth payload that CDP write tools embed on-chain, so an agent knows to use it when on-chain validity matters. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough to guide selection among the sibling price tools.

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