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

With no annotations supplied, the description carries the full burden, and it does disclose the most important operational fact: this is a paid call ($0.002 USDC via x402 on eip155:8453). It also discloses methodology (direct, cross via EUR, peg-derived) and sourcing, which is real behavioral value. However, it omits practical call mechanics — whether payment must be settled before data returns, failure/refund behavior, and caching or rate limits — which matter for a metered 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?

The payment/price banner is correctly front-loaded because it changes whether the agent should call at all, and the substantive sentence follows immediately. The core sentence is dense with parentheticals ('or the official peg when CZK is pegged', 'direct, cross via EUR or peg-derived') but each clause carries information rather than padding.

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?

There is no output schema, so the description must describe the return payload — and it does, listing rate, rate date, method, and source attribution. That covers what an agent needs to decide whether the result is usable for downstream work. What is missing is only the concrete field shape and a sample value, plus any explicit statement of freshness/staleness expectations for a daily fixing.

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 pair and figure type are baked into the tool identity rather than parameterized, which is appropriate here.

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 and direction — 'Official USD/CZK reference rate' — and says exactly which figure it returns (the ECB fixing, or the official peg when pegged). An agent can distinguish it from estimate-based or conversion tools. It stops short of naming a sibling such as fx_czk_usd (the inverse pair) or fx_convert, so direction disambiguation rests on the tool 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: 'Official' and 'Deterministic, sourced, no estimate' signal that this is the authoritative-source option rather than a derived or estimated rate. There is no explicit when-to-use/when-not guidance and no routing to alternatives like fx_convert, fx_latest, or fx_timeseries for historical or conversion needs.

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