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

With no annotations, the description carries the full load and does it well: it discloses the cost and payment protocol ($0.002 USDC/call, x402, eip155:8453), the authoritative source (ECB fixing), the peg fallback behavior, and that results include rate date, derivation method (direct / cross via EUR / peg-derived) and source attribution, plus a no-estimation guarantee. It does not say what happens on non-publication days (weekends/holidays) or how stale the fixing can be, which is material for a daily reference rate.

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?

One dense sentence plus a bracketed cost prefix, front-loaded with the paid/x402 tag and then the resource. Every clause adds information, though the nested parentheticals ('(direct, cross via EUR or peg-derived)') make it slightly harder to scan than it needs to be.

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?

There is no output schema, so the description must describe returns, and it does: rate, rate date, method, source attribution. Combined with the pricing disclosure, an agent has most of what it needs to call and interpret the tool. The gaps are the unstated quote direction (vis-à-vis fx_eur_ils) and freshness behavior on non-fixing days.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description's explanation of returned fields (rate date, method, source) is helpful context but is about output, not parameters.

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?

Names a concrete resource and source: 'Official ILS/EUR reference rate: latest European Central Bank fixing.' That is far more specific than the name alone. It stops short of 5 because it never states the quoting convention (ILS per EUR vs the inverse), and fx_eur_ils exists as a sibling, so an agent cannot tell from the text which direction this tool returns.

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?

Usage is implied rather than stated: 'reference rate', 'deterministic, sourced, no estimate' signals it should be preferred over estimated rates, and the peg clause signals a fallback case. But it never names alternatives (fx_convert, fx_latest, fx_timeseries, fx_eur_ils) or says when to pick this tool over them. No explicit when-not guidance.

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