currency_rates

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

With no annotations provided, the description carries the full burden of disclosure. It only states 'no key' (implying no authentication) and does not mention data freshness, update frequency, source reliability, or any limitations on currency coverage. This is insufficient for an agent to understand the tool's behavior and constraints.

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 two sentences, front-loaded with the primary purpose. It contains no unnecessary words and efficiently conveys the tool's core function and its relationship to sibling tools.

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 tool's simplicity (one optional parameter) and the existence of an output schema, the description is reasonably complete. It covers the essential purpose and default behavior. However, it could benefit from disclosing which currencies are supported or the data refresh interval, making it slightly incomplete but still functional.

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 description coverage is 100%, so the baseline is 3. The description does not add any additional semantics beyond the schema; it only repeats that the base parameter defaults to AED. No extra value is provided.

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 provides 'Everyday exchange rates for a base currency,' with a default of AED. It distinguishes itself from sibling tools like cbuae_exchange_rates by calling itself a 'convenient companion' for everyday use, making its purpose and differentiation evident.

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 context: it's for everyday exchange rates (not official central bank rates), and positions itself as an alternative to the cbuae tools. It does not explicitly list when to use vs. alternatives like currency_convert, but the context is clear enough for an agent to infer appropriate usage.

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