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 price and payment rail ('$0.002 USDC/call, x402, eip155:8453'), the data provenance (ECB fixing, peg-derived fallback), the derivation method (direct, cross via EUR, peg), and that results are deterministic with no estimation. It stops short of describing failure modes, weekend/holiday fixing behavior, or caching/staleness rules.

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 tight sentences with no filler; every clause (price, source, date, method, attribution, determinism) adds information. The billing prefix is front-loaded ahead of the actual purpose, which slightly delays the reader's answer to 'what does this do?' but is defensible for a paid endpoint.

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-arg tool with no output schema, the description does list the returned fields (rate, rate date, method, source attribution), which is the right move. However, the single most consequential output detail for an FX pair — the quote direction/base currency — is absent, and nothing in the schema or annotations can compensate.

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 of 4 applies. The description correctly spends no words on arguments and instead documents what the fixed call returns.

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 verb+resource ('Official NZD/EUR reference rate: latest European Central Bank fixing') and the exact data source, which clearly separates it from non-FX siblings like fx_convert or fx_timeseries. The remaining ambiguity is directional: it never states whether the returned number is NZD per EUR or EUR per NZD, which matters given that a mirrored pair (fx_eur_nzd) exists in the sibling list.

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 only implied through 'latest ... fixing' and 'no estimate', which suggests this is the current point-in-time rate rather than a historical series (fx_timeseries) or a conversion (fx_convert). There is no explicit when-to-use/when-not statement, no mention of alternatives, and no note on what to do for non-EUR-base or pegged-currency cases beyond a parenthetical.

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