get_oracle_price

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that OracleNft reads the oracle UTxO datum, Delisted assets return the delisted price, and Pyth/DeferredValidation delegates to get_pyth_price. This is rich behavioral context beyond what the schema shows, though it does not mention error cases or return format.

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 tightly written sentences. The core purpose is front-loaded, and the parenthetical breakdown of oracle modes adds detail without bloat. Every clause contributes useful information.

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?

The tool is simple: one enum parameter and no output schema. The description covers the main action plus the important edge cases and delegation path. The missing return format or decimal precision is a minor gap for a price-query tool, but the description is otherwise complete enough for correct invocation.

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%, so the description must compensate. It adds the term 'iAsset' to clarify what the 'asset' parameter refers to, and the enum values are self-explanatory. However, it does not provide parameter-specific details such as units, decimals, or behavior differences across the enum values, so compensation is only partial.

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 verb ('Get'), the resource ('on-chain price for an iAsset from its price oracle'), and the three handled oracle modes. It differentiates itself from siblings like get_pyth_price by explaining its broader delegation behavior and from get_asset_price by scoping to iAssets.

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: use this tool to retrieve iAsset prices from their oracle, including special handling for Delisted and delegation to get_pyth_price. It does not explicitly state when NOT to use it or name alternatives, but the oracle-specific framing is enough to guide correct selection among the many sibling tools.

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