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

With no annotations, the description carries the full burden and does meaningful work: it discloses a paid endpoint ($0.002 USDC per call via x402 on eip155:8453), which is critical invocation context an agent could not otherwise know from the empty schema. It also discloses the data provenance, that results are deterministic and non-estimated, and that the payload includes rate date, method, and attribution — though it omits error/fallback behavior when no fixing exists.

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 tight sentences with no filler, and the cost/payment metadata is bracketed up front so it reads immediately. The core purpose sentence is dense but well ordered (rate → source → fallbacks → method → attribution → guarantee).

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 lookup, the description covers provenance, derivation method, freshness ('latest'), determinism, and payment requirement — everything an agent needs to decide to call it. Residual gaps are minor: update cadence and behavior when no ECB fixing is published day-of.

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 no parameter semantics to explain; the baseline of 4 applies. The description correctly implies the pair and source are fixed, consistent with an empty input 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?

States a specific resource ('Official USD/TRY reference rate') and names the exact source (ECB fixing) plus the derivation method (direct, cross via EUR, peg-derived). This clearly identifies what the tool returns, but it never distinguishes itself from adjacent siblings like fx_latest, fx_convert, or fx_timeseries, so the agent must infer the boundary from the pair name alone.

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: 'latest European Central Bank fixing' signals current-spot use and 'no estimate' signals an authoritative rather than modeled figure, which implicitly steers an agent away from modeled or converted-rate tools. There is no explicit when-to-use/when-not guidance and no mention of fx_timeseries for historical needs or fx_convert for amount conversions.

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