calculate_currency_exchange

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

Despite no annotations, the description discloses the computation purpose and lists return fields, providing good behavioral context. It does not mention side effects, but as a calculation tool, destructive behavior is unlikely.

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 a single sentence with return fields and a reference, front-loading the core purpose. No unnecessary 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?

Given the tool's moderate complexity with 4 parameters and output schema, the description covers purpose, return structure, and related tools adequately. No 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?

Schema descriptions cover all parameters (100% coverage), so baseline 3 is appropriate. The description does not add new semantic meaning beyond summarizing the tool's purpose; it reiterates the bank margin concept but doesn't deepen parameter understanding.

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?

Description clearly states it calculates currency exchange including bank margin and fees lost, with a specific verb and resource. It also references related 'voyage' calculators via list_bundles, distinguishing it from siblings like calculate_currency_cross_rate.

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?

Description implies usage for calculating exchange with margin and fees but does not explicitly state when to use this tool over alternatives. The reference to list_bundles provides some guidance but lacks explicit when-to-use or when-not-to-use criteria.

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