calculate_currency_exchange

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

Lists output fields, giving some insight into results. No annotations exist, so description carries burden, but it does not disclose idempotency, side effects, or edge cases like invalid rates.

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 concise sentences: purpose and output description with reference. No fluff, front-loaded.

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?

Output fields are described, but lacks usage context or explanation of 'fees_lost'. No formal output schema. With many similar calculators, more context is needed.

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?

All parameters have schema descriptions (100% coverage). The description adds context about margin affecting fees lost but does not elaborate on parameter usage beyond 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?

Clearly states the tool calculates currency exchange with bank margin and returns various fields. However, it does not differentiate from siblings like calculate_currency_cross_rate or calculate_exchange_margin.

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?

Provides no guidance on when to use this tool versus alternatives among the many calculate_ siblings. Only references list_bundles for voyage calculators, but no exclusions or conditions.

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