get_asset_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 but only specifies the operation is 'current'. It lacks critical details: price denomination (USD/ADA), data source, freshness/caching behavior, return format, or error handling.

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 single sentence is front-loaded with the verb and contains no redundant words. However, extreme brevity comes at the cost of omitting useful behavioral and contextual details.

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 enum parameter, no nesting), the description is minimally adequate but incomplete. The absence of an output schema and annotations creates gaps regarding return value structure and operational side effects that the description fails to fill.

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?

The schema has 0% description coverage and the description only vaguely references 'specific Indigo iAsset' without explaining the enum values (iUSD, iBTC, etc.) or providing examples. However, the term 'iAsset' adds protocol-specific context missing from the schema.

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 action ('Get') and resource ('current price') and specifically targets 'Indigo iAsset', which distinguishes it from siblings like get_ada_price, get_indy_price, and get_asset (which likely returns metadata rather than pricing).

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 no guidance on when to use this tool versus alternatives such as get_asset (for general metadata) or get_ada_price/get_indy_price (for native tokens). No prerequisites or contextual triggers are mentioned.

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