market_data_exchange_rates

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

The description discloses credit costs per action and notes that credits are indicative, with actual credits returned in response headers. Since no annotations are provided, the description carries the burden, but it does not mention whether the tool is read-only, likely response format, or error behavior.

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 well-structured with bullet points for actions and credits, and front-loaded with 'Market Data exchange rates.' The credit list is slightly redundant since both actions cost the same, but overall it remains concise and scannable.

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?

With no annotations and no output schema, the description should provide more context. It lists actions and credits but lacks guidance on parameter grouping, response structure, error handling, or examples. The tool is simple enough that this is acceptable but leaves gaps.

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 already covers all parameters with descriptions, so baseline is 3. The description adds examples like BTC and USD, but does not clarify which parameters are required together or how the action field dictates parameter usage.

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 tool provides exchange rates, with two specific actions 'get-exchange-rate-by-asset-symbols' and 'get-exchange-rate-by-asset-ids' that list the verb and resource. This differentiates it from sibling tools like market_data_metadata, which focus on metadata.

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 makes it clear that exchange rates are the domain, and the two actions are defined with their parameters. However, it does not explicitly state when to use one action over the other or mention alternative tools for non-exchange-rate needs.

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