snb_convert_currency

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which are consistent with a non-mutating conversion. The description adds that it uses the monthly average rate from SNB and returns CHF equivalent, rate, and date, providing additional context beyond annotations.

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 separate sections for purpose, args, returns, and examples. It is not overly verbose, but could be slightly more concise without losing clarity. Every part adds value.

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 input schema, output schema existence, and annotations, the description provides all necessary context: the source of rates, parameter defaults, return format, and example usage. There are no gaps in understanding how to use the 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?

Although the input schema provides descriptions for all parameters (amount, currency_id, reference_month), the description reinforces their meanings with examples (e.g., 'amount=45000, currency_id=USD1') and clarifies defaults. This adds practical value beyond the schema alone.

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 converts foreign currency to CHF using SNB official exchange rates. It specifies the exact rate type (monthly average) and distinguishes from sibling tools that retrieve exchange rates rather than performing conversions.

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 indicates suitability for budget calculations, cost estimations, and financial planning, providing clear use cases. It does not explicitly state when to avoid this tool or mention alternative tools, but the context of sibling tools implies that this is a conversion tool while others are retrieval tools.

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