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 model ($0.002 USDC/call via x402 on eip155:8453), the sourcing policy (ECB fixing, peg fallback), the tiered derivation method (direct, cross via EUR, peg-derived), and the determinism guarantee. It omits operational details an agent may need — whether a payment header must be supplied, and error behavior when no fixing exists for a date.

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 payment bracket, then the resource, source, and output contents in a single dense sentence. Every clause carries information; it is slightly over-packed but has no filler.

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-arg, no-annotations, no-output-schema tool, the description covers source, derivation method, peg handling, as-of date, and attribution — essentially the return payload — plus the cost and protocol. The direction convention is the only remaining ambiguity, and that is minor for a pair-named endpoint.

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 the schema-based baseline of 4 applies. The only semantic gap is that the description does not state the quote direction convention (AUD per PHP vs PHP per AUD), which is the one 'parameter-like' piece of information for a fixed-pair tool.

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 (official AUD/PHP reference rate) with the exact source (ECB fixing) and the fallback case (official peg when PHP is pegged). The currency pair in the name is disambiguated from the ~400 sibling fx_* tools, and the description adds what the value actually is rather than restating the name.

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: call this when you need an authoritative AUD→PHP rate. But it never mentions alternatives that a sibling set this large invites — fx_convert for arithmetic, fx_timeseries for history, fx_latest, or the inverse fx_php_aud — nor when NOT to use it (e.g., non-ECB or intraday rates).

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