get_data_currencies

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds that the call takes no required parameters and returns the full currency set, but omits pagination, caching, or list-size behavior — modest added value on top of rich 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 markdown-heavy format is bloated: the 'What You Get' bullets (currency list, codes, names, country mapping) simply restate the Overview sentence verbatim, and the Quick Start repeats it a third time. Front-loading is fine, but substantial space does not earn its place.

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 parameterless reference lookup with no output schema, the description usefully enumerates the returned fields (ISO codes, names, country mappings), which an agent could not otherwise infer. Nothing critical is missing, though list size and ordering are unspecified.

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?

Only one optional parameter (timeout) with 100% schema description coverage, so the schema already carries the burden. The description's 'No parameters required' is accurate about requiredness but adds no syntax or default guidance beyond what the schema provides.

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?

States a specific verb and resource ('Get all available currencies') with the exact payload: codes, names, and country mappings. It is distinguishable from siblings like get_data_countries and get_data_languages by resource, though it never names an adjacent tool explicitly.

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?

The 'When to Use' section gives four concrete scenarios (dropdowns, price display, conversion, reference data for booking endpoints), which is clear context for invocation. It stops short of explicit exclusions or named alternatives (e.g., 'use get_data_countries for country data'), so it is not a 5.

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