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

Beyond readOnlyHint and openWorldHint, the description discloses the paid-call mechanics that an agent cannot infer: $0.001 USDC per call via x402, that an unpaid call returns the payment requirements rather than failing, and the three accepted payment channels. It also states the payload is returned verbatim as strings, which matters for downstream formatting.

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?

Dense and front-loaded: purpose first, then disclaimers, then pricing and the retry protocol. Minor redundancy between "Information only, not transaction quotes" and "No payment processing", but no sentence is filler.

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 does the work of characterizing the response (attributed, dated, unchanged strings) and covers the payment failure mode, which is the main way this call goes wrong. A short note on the actual response envelope would make it fully self-sufficient for a paid tool.

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 single `currencies` parameter is already fully documented in the schema (uppercase ISO code, EUR returns 1, omit for all rates, max 40), so the description adds nothing on parameters. With 100% schema coverage the baseline of 3 applies.

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?

"Read attributed, dated ECB EUR-base currency reference rates as unchanged strings" gives a specific verb (read) and a precise resource (ECB EUR-base reference rates), plus a scoping qualifier (unchanged strings) that rules out derived/computed FX. The negative framing ("not transaction quotes", "no payment processing") further separates it from any pricing or settlement sibling.

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 clearly sets the use context (reference data / information only, not tradable quotes) and gives an explicit recovery path when the call is unpaid: retry with X-PAYMENT or PAYMENT-SIGNATURE headers or params._meta["x402/payment"]. What's missing is any routing statement toward alternatives (e.g. funding_rate_normalize or erc20_decode) for related rate needs.

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