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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the paid nature and exact price ($0.002 USDC/call via x402 on eip155:8453), the data source (ECB fixing), the fallback behaviour when AED is pegged, and the determinism guarantee. It stops short of describing the payment handshake, error conditions, or update cadence, which for a paid and rate-limited resource would have been the final piece.

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 dense sentences with no filler — pricing first, then substance, then the deterministic/no-estimate qualifier last. Slightly compression-heavy (the bracketed x402/eip155 metadata is opaque), but every clause carries information.

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 tool the description covers what is returned (rate, rate date, derivation method, source attribution), which compensates for the absent output schema. Freshness expectations and failure modes are the only material omissions.

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 meaning to convey; the baseline of 4 applies. The description correctly adds no parameter detail that the empty schema would contradict.

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 gives a specific verb+resource: the 'Official THB/AED reference rate', a single unambiguous currency pair, which is exactly the axis on which the ~500 sibling fx_* tools differ. It does not, however, name the generic alternatives (fx_convert, fx_latest, fx_timeseries) that an agent might otherwise reach for, so sibling differentiation is achieved through the pair name rather than explicit routing language.

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?

There is no explicit when-to-use/when-not-to-use statement. The phrases 'reference rate' and 'no estimate' imply the tool should be preferred when an authoritative sourced rate is required rather than a computed or estimated one, but the agent is left to infer this. Nothing steers the agent between this and fx_convert or fx_timeseries.

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