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

With no annotations, the description carries the full burden and does substantial work: it discloses the $0.002 USDC/call x402 cost on chain eip155:8453, the deterministic non-estimated nature of the value, the peg fallback, and the presence of rate date, method, and source attribution in the response. Gaps remain on failure modes and ECB publication cadence (weekend/holiday behavior), which matter for an agent deciding whether a value is stale.

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 front-loads the payment metadata then states source, fallback, and returned fields with no filler. It is somewhat long for a zero-parameter endpoint, but each clause (cost, source, method, determinism) contributes distinct information.

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 and no annotations, the description is the only documentation, and it partly covers the return payload (rate date, method, source). It omits critical semantics for an FX value: quotation direction (XAF per NZD vs NZD per XAF), rounding/precision, and how non-fixing days are handled — details an agent needs to interpret the number correctly.

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 baseline is 4 and there is no parameter meaning the description could or should add. The pair is fixed by the tool name, so no input ambiguity exists.

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 concrete resource — the official XAF/NZD reference rate — and specifies its provenance (ECB fixing or official peg), which is more than the name alone conveys. It does not, however, distinguish itself from the many sibling pair tools or from fx_convert/fx_latest, leaving that differentiation to the name.

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?

The presence of a paid x402 call and the word 'reference rate' implies this is for authoritative single-pair lookups, but there is no explicit when-to-use guidance and no mention of alternatives such as fx_convert for conversions or fx_timeseries for historical series. Usage is only inferable from the pair encoded in the name.

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