Currency and Country Metadata

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

Beyond the readOnlyHint annotation, the description discloses cost (1 credit per lookup), caching behavior (force_refresh bypasses cache only on user request), and that it works on free and paid plans. No contradictions with annotations.

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 description is well-structured and efficient, covering purpose, cost, returns, parameters, and usage guidance in a few sentences. It is concise but could be slightly shorter; however, every sentence adds value.

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?

Despite no output schema, the description details return fields (currency code/name/symbol, country calling_code, tld, languages) and explains both parameters thoroughly. It also integrates cost, caching, and sibling tool guidance, making it fully self-contained for an agent to use correctly.

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 input schema has 100% description coverage, but the description adds useful context: ip selects the IP used and omitting it uses caller IP; force_refresh should be used only when the user asks and can consume credits. This adds value beyond the schema's brief descriptions.

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 clearly states it is a read-only currency and country metadata lookup via GET /v3/ipgeo. It specifies the return fields and distinguishes from the sibling lookup_ip by advising to use this tool for currency/country metadata only, thus differentiating its purpose.

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?

Explicit guidance is provided: use this tool for currency-only or country-metadata-only requests, and if more IP data is needed, prefer lookup_ip. It also instructs to set force_refresh only when the user asks, covering when to use the parameter.

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