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 substantial work: it discloses the payment model and price ($0.002 USDC/call, x402, eip155:8453), the authoritative source, the peg-fallback behavior, and the guaranteed non-estimated nature of the value. It stops short of stating publication cadence, staleness tolerance, or what happens on payment failure or a missing fixing.

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?

Front-loaded with the cost/payment tag, then the resource, then the source and fallback, then the trust qualifier — a sensible ordering with no filler. It is one long run-on sentence, which makes the payment terms and the data semantics harder to scan than they need 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 and no annotations, so the description must convey the return shape itself, which it does: rate value, rate date, derivation method (direct, cross via EUR, or peg-derived), and source attribution. For a zero-parameter lookup that is close to complete; only freshness/cadence is left unstated.

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 nothing needs explaining; the baseline applies. The description correctly implies the pair is fixed by the tool name rather than passed as an argument.

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 (CNY/JPY reference rate) and a concrete source (European Central Bank fixing), plus the fallback case (official peg when JPY is pegged). With hundreds of fx_* siblings keyed by currency pair, this states unambiguously which pair and which kind of rate an agent is getting.

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 by the pair-specific nature of the tool and the 'no estimate' framing, but the description never names when to prefer it over fx_convert, fx_latest, or fx_timeseries, nor when it is the wrong choice (e.g. needing a historical series or an arbitrary amount conversion).

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