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

With no annotations at all, the description carries the full burden and does well: it discloses the paid x402 gate ($0.002 USDC/call on eip155:8453), the upstream source (ECB fixing), the fallback behavior when NZD is pegged, the returned metadata (rate date, derivation method, source attribution), and that values are deterministic with no estimation. It does not cover publication cadence or what happens on weekends/holidays when no ECB fixing exists, which is the main remaining behavioral gap.

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?

Compact and mostly front-loaded: the pair and rate identity come immediately, with the payment metadata as a bracketed prefix and the return fields in one trailing clause. The single long sentence is dense but every clause carries information; the only friction is that the cost tag precedes rather than follows the purpose statement.

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-parameter, no-annotation, no-output-schema tool, the description supplies what an agent needs to decide and call: source authority, cost and payment rail, determinism guarantee, peg fallback, and the fields returned (date, method, attribution). It stops short of stating freshness limits or error behavior when no fixing is published, which matters for a rate tool.

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; the baseline for a no-param tool applies. The description correctly frames this as a fixed-pair lookup rather than something parameterizable.

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 precise resource and scope: 'Official EUR/NZD reference rate' from the 'latest European Central Bank fixing'. The currency pair in the name is fully disambiguated from the hundreds of sibling fx_* tools, and it states the fallback case (official peg) so the agent knows what value it gets in either regime.

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: 'Official', 'reference rate', 'Deterministic, sourced, no estimate' signal this is for authoritative/reference purposes as opposed to a convenience conversion. However, it never explicitly contrasts itself with fx_convert, fx_latest, or fx_timeseries, nor does it say when to prefer those siblings for conversion or historical series.

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