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 does well: it discloses price and payment scheme ($0.002 USDC/call, x402, eip155:8453), the upstream source (ECB fixing), the fallback logic (peg when AUD is pegged), the derivation method (direct, cross via EUR, peg-derived), and the determinism guarantee ('no estimate'). It stops short of stating behavior when a fixing is unavailable (rate date in the past, holiday gaps) or whether results are cached.

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 sentences, front-loaded with the billing tag then the resource, then the derivation and trust guarantees. Every clause adds information — source, method, fallback, determinism — with no filler or repeated name text.

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 annotations and no output schema, the description does the work of describing the return payload (rate date, method, source attribution) plus cost and sourcing, which is strong for a zero-parameter tool. The notable omission is quotation direction — whether the returned number is AUD per BRL or BRL per AUD — which is the single most consequential ambiguity for a consumer.

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, which is the baseline-4 case; there are no argument semantics to clarify. The description implicitly confirms the pair is fixed by the tool name rather than parameterized, which is the relevant fact an agent needs.

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?

Names a precise verb+resource ('Official BRL/AUD reference rate') with the exact source (European Central Bank fixing), which unambiguously distinguishes it from the hundreds of sibling pair tools like fx_brl_usd and fx_aud_aud. An agent knows exactly which currency pair and which data this returns 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: an agent infers this is the tool for the BRL→AUD pair specifically. It never states when to prefer it over fx_convert, fx_latest or fx_timeseries, nor what to do if a different pair or a historical series is needed. Given an ~800-sibling family, an explicit routing sentence would materially help.

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