list_currencies_catalog

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

No annotations provided, so description carries full burden. It discloses result contents (min/max amounts, decimals, network info, features) and caveats about not showing input_currency_code to users. Lacks details on rate limits or performance, but adequate for a read-only listing tool.

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?

Relatively long but well-structured with sections (USE WHEN, DISPLAY RULES, etc.). Purpose is front-loaded. Each sentence adds value. Slightly verbose but justified by the need for clarity.

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 only one optional parameter and no output schema, the description covers all needed context: usage scenarios, display rules, result details, and network selection. Complete for a catalog listing tool.

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 one parameter filter_by_amount described. Description adds context: 'Optional EUR amount to filter currencies that support this payment amount' and usage example. Adds value beyond the schema's own description.

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 'Get available cryptocurrencies with optional amount filtering.' The verb 'Get' and resource 'available cryptocurrencies' are specific. It distinguishes from sibling tools like create_payment_onchain by specifying that 'input_currency_code' should only be used in that tool, not shown to users.

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?

Explicit 'USE WHEN' section lists two scenarios: when user asks which cryptos are available, and before onchain payment if crypto has multiple networks. Provides display rules and network selection guidance, making it clear when and how to use the tool vs alternatives.

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