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 cost and payment rail ($0.002 USDC via x402 on eip155:8453), the upstream source (ECB), the fallback behavior for pegged CZK, and that the result is deterministic rather than estimated. It omits edge behavior such as weekend/holiday fixings and any caching or freshness window.

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 with the payment metadata front-loaded in a bracket prefix, followed by the substantive rate description — well front-loaded and free of filler. The bracket notation is compressed to the point of near-opacity for a reader unfamiliar with x402, but it is information-dense rather than wasteful.

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 annotations and no output schema, the description supplies the key facts an agent needs: source, method, rate date, attribution, and cost. It stops short of naming the response fields or explaining publication cadence, which matters somewhat given no output schema exists.

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 and the baseline applies. The description correctly implies the pair and rate basis are fixed by the tool identity rather than supplied as arguments.

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 and pair — "Official CNY/CZK reference rate" — plus the data source (ECB fixing) and derivation method, which distinguishes it from the hundreds of sibling pair tools and from generic tools like fx_latest or fx_convert. An agent knows exactly what this returns without opening a schema.

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 description implies when to use it (need an official, sourced, non-estimated CNY/CZK rate) and discloses the paid x402 cost, which is useful routing context. However it never names alternatives (fx_convert, fx_latest, fx_timeseries) or states when-not to use it, so the agent must infer the choice from the pair name alone.

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