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

With no annotations, the description carries the full behavioral burden, and it does disclose meaningful traits: a $0.002 USDC per-call x402 payment on eip155:8453, the ECB as source, peg-derived fallback behavior, and the returned provenance fields (rate date, method, attribution). It does not say whether the result is cached, how stale the fixing can be, or what a payment failure looks like, so it is useful but incomplete for a paid endpoint.

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?

It is a single dense sentence, front-loaded with the payment header and then the core purpose and provenance details. Almost every clause earns its place, though the payment bracket competes for attention ahead of the actual purpose.

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 lookup with no output schema, the description covers source, method, peg fallback, and the fields returned, plus payment cost. It lacks only freshness cadence and error/payment-failure behavior, which are minor for this complexity level.

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 the baseline is a 4. The description correctly adds no parameter noise and instead explains the returned fields, which is the relevant semantic detail for a no-arg call.

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 states a specific verb+resource: it returns the official XOF/ZAR reference rate, sourced from the latest ECB fixing. It also clarifies the fallback case (official peg when ZAR is pegged) and what the payload carries. It does not explicitly name sibling alternatives like fx_convert or fx_latest, so it stops short of full sibling differentiation.

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?

There is no when-to-use or when-not-to-use guidance. An agent is not told when to prefer this pair endpoint over fx_convert, fx_latest, or fx_timeseries, nor that other pairs live under the fx_<BASE>_<QUOTE> naming convention. Usage is only implied by the tool name and the currency pair.

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