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

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses a paid x402 endpoint ($0.002 USDC/call on eip155:8453), the upstream authority (ECB fixing), the derivation method (direct, cross via EUR, or peg-derived), and that values are deterministic with no estimation. It stops short of stating fixing frequency/refresh cadence or what happens outside ECB publication days, which matters for a rate tool.

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?

One tightly packed sentence that front-loads cost/payment rail, then the resource, then the derivation and provenance guarantees. There is no filler or repetition.

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, yet the description names the return payload components (rate, rate date, method, source attribution) and rules out estimation, which is most of what an agent needs. The remaining gap is freshness semantics, since an ECB fixing is periodic and staleness is the main risk an agent would want disclosed.

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 and the baseline applies. The description correctly conveys that base and quote are fixed by the endpoint itself rather than supplied by the caller.

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?

States a precise verb+resource: the official AUD/USD reference rate, specifically the latest ECB fixing, with the peg fallback called out. Combined with the pair-specific tool name, an agent can tell it apart from fx_convert, fx_latest, fx_timeseries and the other ~900 fx_* pairs without opening any schema.

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 by the name and the 'reference rate' framing; there is no explicit when-to-use versus alternatives such as fx_convert (for conversion math) or fx_usd_aud (inverse direction). The agent must infer that this returns a single official fixing rather than a converted amount or a time series.

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