ECB FX Reference Rates

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

With no annotations, the description carries the full burden and largely meets it: it discloses the fallback behavior (previous business day if no rate that day), what is returned (ECB reference date, raw EUR rates, source link), and the paid-per-call x402/USDC-on-Base billing model. It omits failure modes (invalid currency, pre-1999 date) and payment-negotiation flow, keeping it from a 5.

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?

Three sentences, front-loaded with the resource and scope before the usage context and billing note. Every sentence carries information; the length is justified by the multi-mode capability (rates, cross rates, conversion) but is slightly dense.

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?

With no output schema, the description steps in to describe the return payload (reference date used, raw EUR rates, source link), and it discloses the payment model. That covers what an agent needs to call and interpret results, though error/edge-case behavior and the payment-signature handshake are left implicit.

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 adds meaning beyond the schema by framing base as driving cross rates and amount as a conversion input, and by bounding the date range ('since 1999'), which clarifies valid date values and the symbols scope (~30 currencies).

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 states a specific resource (official ECB euro foreign exchange reference rates), its scope (~30 currencies, latest business day or any date since 1999), and the added capabilities (base-currency cross rates and amount conversion). An agent immediately knows what the tool fetches and what it computes on top.

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?

It gives a clear when-to-use context: official, citable rates for invoicing, accounting, VAT/tax returns or reporting, for today or any business day since 1999. There are no siblings and no explicit when-not or alternative conditions, so it stops short of a 5.

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