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

Adds substantial behavior beyond the annotations (readOnly/idempotent/openWorld): the 366-day cap, working-day granularity, ECB source, re-basing support, per-currency aggregates, and crucially the x402/USDC pricing model with the PaymentRequired fallback. The payment semantics are non-obvious and fully disclosed.

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, fully front-loaded: use case first, output shape second, payment requirement last. No filler, and the most decision-relevant detail (paid, $0.002) is stated plainly.

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 carries the burden of explaining returns and does so explicitly (first, last, min, max, percent change per currency), plus the range cap and payment flow. Nothing an agent needs to call correctly is missing.

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%, so the baseline is 3, but the description adds constraints the schema omits — the max 366-day window on start/end and the re-basing behavior tied to base. Symbols' 10-item cap is echoed from the schema, so the marginal value is modest but real.

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?

States a specific verb and resource — returns daily ECB reference rates between start and end — and front-loads the two use cases (trend questions, back-dated conversions). An agent can distinguish this from fx_latest (current snapshot) and fx_convert (forward conversion) without opening the schema.

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?

Gives clear context for when to reach for this tool: trend questions and back-dated conversions. The date-range framing implicitly separates it from fx_latest, but it never names the sibling alternatives or states exclusions explicitly, 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.