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 cost ($0.002 USDC/call via x402 on eip155:8453), the upstream source (ECB fixing), the fallback behavior when BGN is pegged, and that the response includes rate date, derivation method and source attribution. It stops short of stating freshness/staleness behavior, weekend-holiday handling, or what happens on error.

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 cost and then the substance; every clause (source, method, date, attribution, determinism) adds information. The bracketed x402 payment preamble is slightly noisy but is genuinely decision-relevant for an agent that must pay per call.

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 and no annotations, the description covers source, derivation method, cost, and the fields returned, which is close to complete. The remaining gap is temporal behavior: it never says how fresh the fixing is, how often it updates, or what happens on non-TARGET business days.

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 and the baseline is 4. The description usefully spends that space on the fixed pair and the derivation method that determine the returned rate instead.

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 a specific resource (the USD/BGN pair) and a specific data product (the official ECB fixing, or the peg when BGN is pegged), so an agent knows exactly what value comes back. It does not, however, say anything about the ~1000 sibling pair tools or point to fx_latest / fx_convert, so the differentiation burden falls entirely on the tool name.

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?

"Deterministic, sourced, no estimate" implicitly tells the agent to use this when an official reference rate is required rather than a speculative or intraday quote, which is a real usage signal. But there is no explicit when-to-use versus fx_convert, fx_latest, fx_timeseries, or the inverse pair fx_bgn_usd, and no stated conditions or exclusions.

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