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

With no annotations supplied, the description carries real weight: it discloses the paid access model ($0.002 USDC/call via x402 on eip155:8453), the data provenance, the deterministic/non-estimated nature, the peg fallback, and the presence of rate date, method, and attribution in the response. What it omits is freshness latency (how quickly the latest ECB fixing becomes available) and failure behavior for unsupported or non-published dates.

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?

One dense sentence plus a short qualifier, with the cost/write-model banner front-loaded so an agent sees the payment requirement before anything else. Every clause adds information, though the bracketed payment metadata slightly crowds out the core purpose statement.

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 — and it does, enumerating rate date, method (direct, cross via EUR, or peg-derived), and source attribution. For a zero-parameter lookup this is nearly complete; the remaining gaps are quote-direction convention and staleness expectations against the ECB publication calendar.

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 for the description to add; the baseline of 4 applies but is tempered by one substantive ambiguity — the description never states quote direction (INR per GBP vs GBP per INR), which is the single semantic detail a caller of a fixed-pair FX tool actually needs.

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 (INR/GBP reference rate), the authoritative source (European Central Bank fixing), and the fallback behavior (official peg). It does not explicitly differentiate itself from siblings like fx_convert, fx_latest, or fx_timeseries, but the pair-specific naming plus 'reference rate' versus 'conversion' makes the intent reasonably unambiguous.

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?

Implicit guidance is present in 'Deterministic, sourced, no estimate' — signaling this tool is for authoritative reference rates rather than derived or estimated conversions. However there is no explicit when-to-use versus fx_convert (for conversion math), fx_latest (for multi-pair snapshot), or fx_timeseries (for history), and no stated prerequisites beyond the payment note.

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