Convert currency (live rates)

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states that exchange rates are live and refreshed every 6 hours, which is a useful behavioral detail. However, it does not mention potential errors, network dependencies, or output specifics, leaving some transparency gaps.

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 brief and well-structured: three short sentences, with the main purpose front-loaded. Each sentence provides distinct value (purpose, input format, usage guidance) with no redundancy.

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?

For a simple three-parameter tool with no output schema, the description covers the core functionality, input requirements, and usage context. It doesn't explicitly describe the return format, but 'convert' implies the converted amount, which is likely sufficient. Slightly more detail on output could improve completeness.

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 provides descriptions for 'from' and 'to' but not for 'value'. The description clarifies that the tool converts an amount, implying 'value' is the monetary amount. It also reinforces the ISO 4217 code format for currency parameters, adding value beyond the 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?

The description clearly states the tool converts an amount between currencies using live exchange rates. It distinguishes from sibling tools (convert_units) by explicitly mentioning currency and live rates. The verb 'Convert' is specific and matches the tool name.

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 explicitly says 'Use this instead of estimating rates from memory,' providing clear guidance on when to use the tool (when live rates are needed) and when not to (avoid manual estimation). It doesn't explicitly mention sibling tools, but the context makes the intended use clear.

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