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

With no annotations, the description carries the full burden and does well: it discloses the paid x402 micropayment ($0.002 USDC on eip155:8453), the authoritative source, the deterministic/no-estimate policy, and that peg-derived values are flagged via the method field. It stops short of covering failure modes (e.g. non-trading-day behavior) or how the rate is delivered, which keeps it below a 5.

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 preceded by a bracketed cost/transport tag — no repetition and no filler. The closing fragment 'Deterministic, sourced, no estimate' is slightly promotional but still conveys a real behavioral 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 tool, the description covers source, currency pair, cost, and returned metadata adequately. The one genuine gap is that quote direction (SAR base, BGN quote) is implied by the name rather than stated.

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 4 applies. The description does add useful semantic context by explaining that the rate method and date come back with the value rather than being caller-specified.

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 (SAR/BGN reference rate), names the exact source (European Central Bank fixing) and what is returned (rate date, derivation method, source attribution). Because each currency pair has its own sibling tool, naming the pair unambiguously distinguishes this from the hundreds of fx_* alternatives.

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 only implied by the pair name — an agent infers 'call this when you need a SAR-to-BGN rate'. There is no explicit statement of when to prefer this over fx_convert, fx_latest, fx_timeseries, or the inverse fx_bgn_sar, and no exclusion or prerequisite guidance.

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