Get Currencies

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

No annotations are provided, but the description states 'Public — no credentials required', which is valuable authorization context. 'Fetch' implies a safe, read-only operation, and the mention of v2 format discloses a behavioral option, though it doesn't detail multi-chain behavior beyond the schema.

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 sentences deliver the purpose and key usage hints without wasted words. Front-loaded with the main action.

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?

The tool is simple (3 parameters, no output schema), and the description covers purpose, key parameter behavior, and auth. It lacks explicit return-value detail beyond 'chain/network details', but that's sufficient for a low-complexity tool.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the effect of omitting 'currency' and setting 'v2', which goes beyond the schema's simple 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 uses the specific verb 'Fetch' with the resource 'supported currencies and their chain/network details', clearly distinguishing it from sibling tools like get_ticker or get_balances. It also explains the optional currency parameter for singular vs all.

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?

It provides clear context that omitting 'currency' returns all currencies and that setting 'v2' changes the response format. It does not explicitly name alternative tools for exclusion, but the context is sufficient for a distinct get_currencies function.

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