get_asset

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

No annotations provided, so description carries full disclosure burden. While 'Get' implies read-only, the description omits safety details (idempotency, side effects), return value structure (what 'details' includes), and error behaviors. Lacks context on the Indigo protocol domain.

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?

Single sentence with no filler. Appropriately brief for a simple getter, though arguably too terse given the complete lack of schema documentation and the need to distinguish from numerous sibling tools.

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?

Adequate for a single-parameter lookup tool with no output schema, but incomplete given 0% schema coverage. The description should specify what constitutes 'details' (metadata, price, supply?) to distinguish from 'get_asset_price' and compensate for undocumented parameters.

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 has 0% description coverage. The description adds context that the parameter refers to a 'specific Indigo iAsset', which helps interpret the 'asset' parameter, but fails to document the four valid enum values (iUSD, iBTC, iETH, iSOL) or explain that these represent synthetic/indigo-wrapped assets.

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?

Clear verb ('Get') and resource ('details for a specific Indigo iAsset'), identifying it as a retrieval operation for Indigo protocol synthetic assets. However, it fails to differentiate from sibling 'get_assets' (plural) or 'get_asset_price', leaving ambiguity about what specific 'details' are returned versus price or list data.

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?

No guidance provided on when to use this single-asset lookup versus 'get_assets' (batch retrieval) or 'get_asset_price' (specific metric). No mention of prerequisites, required permissions, or error conditions (e.g., invalid asset symbols).

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