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

With no annotations supplied, the description carries the full burden and does well: it discloses the paid x402 flow, the exact price ($0.002 USDC), the chain (eip155:8453), the authoritative source (ECB), and that pegged regimes fall back to an official peg. It also promises determinism and explicitly disclaims estimation. It stops short of stating refresh cadence, stale-rate behavior, or what happens on payment failure.

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?

A single dense sentence plus a bracketed billing header — every clause earns its place (pair, source, peg fallback, returned metadata, method, attribution, determinism). The cost/protocol prefix is front-loaded so the agent sees the payment obligation before committing.

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?

No output schema exists, and the description compensates by enumerating the returned elements: the rate, the rate date, the derivation method (direct, cross via EUR, peg-derived), and source attribution. Combined with the payment disclosure, that is nearly complete; the main gap is the absence of any stated freshness or update-time expectation for an ECB daily fixing.

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 the schema imposes nothing to explain and the baseline of 4 applies. The description appropriately spends its words on output semantics and payment requirements instead of inventing parameter guidance.

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 names the exact resource — the official XAF/ILS reference rate — and specifies the underlying source (European Central Bank fixing, or the official peg). That is far more specific than tautology. It does not, however, distinguish itself from sibling routing tools such as fx_convert, fx_latest, or fx_timeseries, leaving the agent to infer the division of labor from the pair-encoded name alone.

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: an agent can tell this returns the current XAF/ILS fixing, and the x402 price header signals it is a paid per-call endpoint. There is no explicit guidance on when to pick this over fx_convert (conversion), fx_latest (multi-pair snapshot), or fx_timeseries (history), and no stated preconditions beyond payment.

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