Get all currencies

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and side effects. The description adds that it targets a specific administration and includes exchange rates, which is context beyond the annotations but not a deep behavioral disclosure (e.g., pagination, result size).

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 contains three lines but the first two largely repeat the same idea ('Get all currencies' vs 'Get a list of all currencies...'). The API path line is informative but redundant. It is concise but not tightly structured due to duplication.

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 simple read-only list tool with zero required parameters and full schema documentation, the description sufficiently explains what is returned (all currencies with exchange rates for the administration). No output schema exists, but the description covers the essential return content. Minor gaps like pagination are not critical for this simplicity.

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 description coverage is 100% for the single optional parameter, including an enum and a clear description. The tool description does not add further parameter-specific semantics, so baseline 3 is appropriate.

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 a specific verb ('Get') and resource ('currencies'), and explicitly states the scope: 'configured for this administration, including exchange rates'. This clearly distinguishes it from other list tools like list_administrations or list_relations.

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 description implies its use for retrieving currency data but does not provide explicit when-to-use guidance or mention alternatives. While the intent is clear, there is no direct comparison to sibling tools or conditions for choosing this over another.

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