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

With no annotations, the description carries the burden and does well: it discloses the paid x402 payment requirement (eip155:8453), the authoritative source (ECB), the fallback behavior when CNY is pegged, and that results are 'deterministic, sourced, no estimate' rather than modeled. It omits failure/caching behavior, so not a 5.

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?

The payload is two sentences front-loaded with the payment tag and the exact resource, and every clause (rate date, method, source) maps to returned data. The bracketed payment metadata at the front is slightly noisy but is genuinely selection-relevant.

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?

There is no output schema, so the description must describe returns itself, and it does: the rate value, the rate date, the derivation method (direct, cross via EUR, peg-derived), and source attribution. Combined with explicit payment terms, this is nearly complete for a zero-parameter lookup, though error and freshness/timing behavior are unstated.

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 description cannot add parameter meaning; baseline 4 applies. It correctly frames the fixed pair rather than implying any inputs are needed.

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 names the exact resource and pair ('Official PHP/CNY reference rate') and identifies the source and derivation method, so an agent can tell it apart from the hundreds of sibling fx_php_* and fx_*_cny tools purely from the name plus this text.

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 cost line ('PAID $0.002 USDC/call, x402') gives a real selection signal for a paid tool, and the 'latest ECB fixing' phrasing implies spot-rate use. However, it never states when to prefer this over fx_convert, fx_latest, or fx_timeseries, nor does it say what happens for historical or converted amounts.

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