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

Annotations are sparse (readOnlyHint=false, openWorldHint=true, destructiveHint=false), and the description carries the burden well: it discloses pricing ($0.01 USDC on Base), the Shelf Pass ceiling (≤$0.25) above which credits are not spent, the x402 v2 payment_required fallback, and the source-blend caveat plus as_of/fetched_at fields. This is rich behavioral disclosure consistent with readOnlyHint=false.

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?

Front-loaded with the core purpose and currency list, then payment mechanics, then a useful negation ('does not return the rate as a bare payment link'). Dense but every sentence mostly earns its place; the title repeated as the opening sentence is minor redundancy.

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?

No output schema exists, and the description compensates by naming the response fields (source, as_of, fetched_at) and the payment-failure shape. It is nearly complete for a paid single-pair fetch, though it omits error behavior for an unsupported/invalid pair.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the pass ceiling rule ('above the pass ceiling the token is not spent') and the pricing context that gives the pass_token parameter its purpose. The pair format itself is only in the schema, so it isn't a full 5.

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 states a specific verb, resource and scope — the official USD reference rate for exactly one African currency — and enumerates the supported currencies (KES, NGN, GHS, TZS, UGX, ZAR, EGP, RWF). The word 'official' plus the blend-vs-fixing clarification cleanly separates it from the sibling get_fx_parallel without opening either 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?

It explains the payment/eligibility conditions under which data is returned versus a payment_required response, which is real usage context. However, it never tells the agent when to prefer this tool over get_fx_parallel or get_fx_africa_brief; the distinction is left to be inferred from 'official'.

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