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 a per-call charge ($0.002 USDC), the x402 payment mechanism, the settlement chain (eip155:8453), the authoritative data source (ECB fixing), the peg fallback path, and the determinism/no-estimate guarantee. It does not cover failure modes, staleness guarantees, or what happens on non-publishing days, which keeps it below a 5.

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 compact sentences that front-load the material facts — price and payment scheme first, then what the rate is and how it is derived. No filler, and the hedge-free wording ("deterministic, sourced, no estimate") is efficient.

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?

For a zero-argument, no-output-schema tool, the description tells the agent essentially everything needed to decide and call: source, method, included metadata (rate date, method, attribution), and the cost. Missing only the concrete response field names and a note on refresh cadence/settlement-day behavior, which is a modest gap rather than a blocking one.

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 parameter-semantics baseline is 4; the currency pair is fixed by the tool identity rather than by input. The description adds useful context about the rate's provenance even though there are no arguments to explain.

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 a specific resource and pair ("Official CNY/TRY reference rate") and specifies the underlying source and method (ECB fixing, cross via EUR, peg-derived), which goes well beyond the tool name. It does not, however, distinguish itself from nearby alternatives such as fx_convert, fx_latest, or fx_timeseries, so an agent must infer that this is the canonical single-pair spot lookup.

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: "no estimate" hints that this is for authoritative reference rates as opposed to computed or approximated conversions, and the price tag signals a paid call. There is no explicit when-to-use/when-not guidance and no routing to fx_convert for arithmetic conversion or fx_timeseries for history, which matters given the very large sibling set.

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