Currency Conversion Tool

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 mentions using 'latest exchange rate', which hints at real-time or recent data, but doesn't disclose critical behavioral traits such as rate limits, error handling (e.g., invalid currency codes), data sources, or whether the conversion is approximate or exact. This is a significant gap for a tool with no annotation coverage.

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, efficient sentence that directly states the tool's function without any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 complexity of currency conversion (which involves external data sources and potential errors) and the lack of annotations and output schema, the description is incomplete. It doesn't cover return values, error cases, or behavioral constraints, leaving the agent with insufficient information to use the tool effectively in a real-world context.

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 description coverage is 100%, with clear descriptions for all three parameters (amount, from_currency, to_currency). The description adds minimal value beyond the schema, as it only reiterates the conversion action without providing additional context like currency code formats or examples beyond what's implied. Baseline 3 is appropriate when the schema does the heavy lifting.

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 purpose with a specific verb ('convert') and resource ('amount from one currency to another'), and mentions the use of 'latest exchange rate'. However, it doesn't explicitly differentiate from sibling tools like 'calculatePortfolioValue' which might also involve currency conversion, though the distinction is somewhat implied by 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, limitations (e.g., supported currencies), or comparisons with sibling tools that might handle financial data. This leaves the agent without context for tool selection.

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