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

No annotations exist, so the description carries the full burden, and it does disclose substantial behavior: per-call cost ($0.002 USDC), the x402 payment mechanism, the chain (eip155:8453), the peg fallback logic, the derivation method (direct, cross via EUR, or peg-derived) and source attribution. It stops short of explaining behavior on non-fixing days (weekends/holidays) or what a failure/payment-required response looks like.

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 plus a short qualifier, with no filler. The payment/transport prefix occupies the front position rather than the rate purpose, which is slightly suboptimal for front-loading, but the bracket convention makes it skimmable.

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, no-output-schema tool, the description covers what is returned at a conceptual level: the rate, its date, the derivation method and the source attribution. The main residual gap is publication cadence and behavior on non-fixing days, which matters for a rate tied to a weekday ECB schedule.

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 does clarify that the pair is fixed rather than configurable, which reinforces the empty schema.

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 the exact resource (AUD/TRY reference rate), the authority behind it (European Central Bank fixing) and the fallback (official peg when TRY is pegged). The currency pair in the text is what separates it from the hundreds of sibling fx_* pairs. It lacks an explicit retrieval verb, but the intent is 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?

The phrase 'Deterministic, sourced, no estimate' implies this is the authoritative source to prefer over derived or estimated rates, which is useful context. However, it never names alternatives such as fx_convert, fx_latest or fx_timeseries, nor does it state when a caller should choose this single-pair fixing instead of converting an amount.

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