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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the paid x402 gate ($0.002 USDC/call on eip155:8453), the data source (ECB), the fallback semantics (peg-derived when AUD is pegged), the derivation method (direct or cross via EUR), and that the value is deterministic with no estimation. It stops short of stating failure behavior when no fixing exists or whether the result is cached.

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?

It is a single tight sentence with the payment gate front-loaded and the substantive purpose immediately after, and every clause (rate, date, method, attribution) adds information. The bracketed pricing block is arguably metadata rather than purpose, but it is a necessary precondition the agent must see before calling.

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, single-value tool with no annotations and no output schema, the description covers everything needed: what the number is, where it comes from, how it was derived, what accompanies it, and what it costs to call. An agent can decide and invoke without further questions.

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 semantics to explain and the baseline of 4 applies. The description correctly spends no words on inputs and instead describes the shape of the returned data.

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 (KRW/AUD reference rate) and pins the provenance (latest ECB fixing, or the official peg when AUD is pegged), so an agent knows precisely which pair and which kind of number it gets. It does not explicitly contrast itself with the generic siblings (fx_convert, fx_latest, fx_timeseries), but the currency pair embedded in the name and description is enough to disambiguate within the fx_* family.

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 when-to-use or when-not-to-use guidance and no mention of alternatives such as fx_convert for arbitrary conversion, fx_latest for the newest rate, or fx_timeseries for history. The only implicit routing signal is the hardcoded pair, which comes from the tool name rather than the description text.

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