convert_currency

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

Discloses that rates must be caller-supplied and USD-based, and provides example format. No annotations exist, so description carries full burden; it covers key behavioral traits but omits error handling details.

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?

Two sentences plus example, front-loaded, every sentence adds value. No wasted 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?

No output schema; description omits return format and error conditions (e.g., missing currency in rates). Adequate for a simple conversion but could be more complete.

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% (baseline 3). Description adds meaning beyond schema: explains rate dict structure (units-per-USD), provides example, and clarifies that amount is in source currency.

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?

Description clearly states verb (convert), resource (amount between currencies), and mechanism (caller-supplied USD-based rates). Distinguishes from siblings as no other sibling performs currency 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?

Explicitly requires caller to provide rates and gives example. No alternative tool for this function among siblings, so context is clear, but lacks explicit when-not-to-use guidance.

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