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

With no annotations, the description carries the full load and does well: it discloses the paid x402 model ($0.002 USDC/call on eip155:8453), the data source and derivation method, and the pegged fallback path, plus an explicit determinism/no-estimate guarantee. It omits freshness/caching behavior and what happens when a fixing is unavailable, but the behavioral picture is substantially clearer than the annotations alone.

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, front-loaded with the gating cost/payment constraint before the data semantics. Every clause carries information — source, method, fallback, attribution, determinism — with 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-parameter read with no output schema, the description covers the return payload's key fields (rate date, method, source attribution) and the pricing gate, which is what an agent needs before calling. Rate units and freshness bounds are the remaining gap, but they are minor at this complexity.

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 add; the baseline for a parameterless tool applies. The description correctly signals a no-argument call with everything fixed by the tool name.

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 a specific resource and direction ("Official INR/CNY reference rate") with the authoritative source (ECB fixing) and the fallback (official peg). An agent can tell what it retrieves and in which direction. It stops short of differentiating from siblings like fx_convert or fx_latest, which also touch this pair.

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 or when-not-to-use guidance, and no alternative is named despite fx_convert, fx_latest, and fx_timeseries existing in the same family. The agent must infer that this is the single-pair official-fixing lookup rather than a conversion or time series.

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