convert_currency

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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral trait (use of Wise exchange rates), which adds specificity. However, it does not describe the return value, handling of source=target, or whether the result includes the rate, leaving gaps for an agent to infer.

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, concise sentence that is front-loaded with the action and object. It contains no filler and every word contributes to the meaning.

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 tool has no output schema and no annotations, so the description must explain what is returned. It does not mention the return format or that the date parameter is optional (though in schema). This leaves the agent without a complete picture of the tool's behavior.

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 coverage is 100%, with descriptions for all four parameters. The tool description adds no new parameter meaning beyond what the schema already provides—it simply reinforces the role of amount and currencies. Baseline 3 is appropriate.

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's verb ('Convert'), resource ('an amount from one currency to another'), and a differentiator ('using Wise exchange rates'). This unambiguously distinguishes it from the sibling tool list_currencies, which lists currencies rather than converting them.

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 the sibling tool name makes the alternative clear (list_currencies for listing). However, it does not explicitly state when to use (e.g., 'Use this for converting amounts') or exclude cases like when historical rates are needed, though the schema partially covers the date parameter.

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