List Markets

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only the sequencing hint about validating symbols first; it says nothing about return shape, result size, or whether markets are cached/refreshed, so it adds modest value beyond structured data.

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?

Two short sentences with zero redundancy; the core purpose is front-loaded and the workflow hint follows immediately. Nothing could be removed without losing 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?

For a simple two-parameter lookup with no output schema and full annotation coverage, the description suffices to call it correctly. A brief note on what the result contains (symbols only vs. pairs with metadata) would close the last gap.

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% with both parameters enum-constrained and documented, including the IRT default. The description restates the quote-currency dimension ('against Toman (IRT) or USDT') but adds no format or validation detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('List the coins an exchange trades against Toman (IRT) or USDT') with scope narrowed to two quote currencies. This is clearly distinguishable from sibling market-data tools like ic_get_ticker or ic_get_orderbook, which retrieve prices rather than symbol inventories.

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?

Explicitly says to use it to 'check a coin symbol before calling the other tools,' which gives an agent a concrete workflow trigger. It does not name the closest alternative (ic_list_exchanges) in the description text, nor state when not to use it, so it falls short of a 5.

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