convert_currency

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

With no annotations, the description carries full responsibility for behavioral disclosure. It adds value by revealing the PLN intermediary mechanism, but does not discuss error handling, rounding behavior, or rates availability on holidays/weekends, which are relevant for a currency conversion 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?

The description is a single, focused sentence that immediately names the action ('Convert an amount') and packs in the key details (rate source, intermediary, date flexibility) without extraneous words.

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?

The description covers the core operation and a significant detail (PLN intermediary), but because there is no output schema, it omits any mention of the return format or behavior on invalid input. This is a moderate gap for a tool with four parameters and no structured output metadata.

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 provides 100% coverage with clear parameter descriptions. The description adds the PLN intermediary detail, which clarifies how from/to interact, but it otherwise repeats the default-date information found in the schema, so the added value is modest.

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 an amount between two currencies, using official NBP mid rates via PLN as intermediary. This distinguishes it from sibling tools like get_exchange_rate, which likely just retrieves a rate rather than performing a conversion.

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 implies usage for currency conversion, and mentions flexibility for today or a specific date. However, it does not explicitly state when to use this tool versus get_exchange_rate, nor does it mention limitations such as unsupported currencies or rate availability.

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