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

With no annotations, the description carries the full burden and does substantial work: it discloses the paid x402 model ($0.002 USDC/call, eip155:8453), the data source (ECB fixing or official peg), the derivation method (direct, cross via EUR, peg-derived), and that output is deterministic and non-estimated. It stops short of describing the response envelope or failure behavior when a fixing is unavailable.

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-loads the payment/transport metadata in a bracket, then the purpose, source and derivation logic in one dense but readable sentence. Every clause carries information; the only minor cost is that the pricing bracket precedes the purpose, slightly delaying the core identification.

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 covers the essentials an agent needs: what rate, which source, which derivation path, what fields come back (rate date, method, attribution), and the payment requirement. Nothing material is missing for correct invocation.

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 4 baseline applies. The mention of rate date, method and source attribution is useful for interpreting the result rather than for invocation.

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 verb+resource: 'Official PHP/AED reference rate' sourced from the ECB fixing, including the fallback case (official peg). The pair direction is unambiguous against siblings like fx_aed_php, but it does not explicitly contrast itself with fx_latest, fx_convert or fx_timeseries, which an agent may also consider.

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: it is the tool for the official PHP/AED reference rate, and the 'no estimate' phrasing hints it should be preferred over derived/approximate sources. There is no explicit when-not guidance, no mention of when to use fx_aed_php for the inverse direction, and no pointer to fx_convert for actual conversion math.

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