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 well: it discloses the paid model ($0.002 USDC/call), the x402 payment protocol, the settlement network (eip155:8453), the upstream source (ECB), the derivation method (direct, cross via EUR, or peg-derived), and that values are deterministic with no estimation. Gaps remain around error/failure behavior when no fixing exists and update cadence, but the disclosure is well above baseline for a parameterless read 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?

A single dense sentence that front-loads the cost/payment bracket before the substantive definition, so an agent knows it is a paid call before reading further. The bracket syntax is slightly noisy, but no sentence is wasted.

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 rate lookup with no output schema, the description covers source, method, date handling, and attribution — enough to call it correctly. It stops short of describing the response shape (field names, quote direction convention, decimal precision), which matters slightly more here because no output schema exists.

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; baseline of 4 applies. The description instead spends its words on provenance and return semantics.

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 specific verb+resource: 'Official XAF/BGN reference rate' from the 'latest European Central Bank fixing', and even covers the peg alternative for BGN. It does not explicitly distinguish itself from nearby siblings like fx_convert, fx_latest, or fx_timeseries, but the pair-specific naming and 'reference rate' framing make the purpose unambiguous.

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: an agent can infer this is the tool for an authoritative XAF→BGN rate, and 'Deterministic, sourced, no estimate' hints at preferring it over computed rates. However, no sibling is named and there is no when-not-to-use guidance versus fx_convert (for arbitrary amounts) or fx_latest/fx_timeseries (for other pairs or history).

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