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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — no indication of what the response contains (a currency list? codes plus symbols?), pagination, or caching/auth behavior.

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?

Brief, but the identical sentence is repeated verbatim twice, wasting half the text on duplication. The remaining token of value (the describe_operation pointer) is buried after the redundant line rather than front-loaded.

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?

No output schema, 0% parameter coverage, and no statement of what is returned. For an endpoint with a free-form query object, the description should at minimum say what the payload looks like and whether query accepts any options; it does neither.

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 0% and the description provides no parameter guidance at all. The schema exposes a free-form `query` object and an empty `params` object, so an agent gets no signal about whether filtering, pagination, or any accepted query keys exist.

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 restates the endpoint path, which does convey the resource (supported currencies within global settings) and implies a read. However, it is essentially a tautology of the name/title and never states in plain language what the tool returns or how it differs from sibling global-settings tools like get_global_settings_currency_config.

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 guidance on when to use this versus related currency/global-settings tools. The only routing hint is 'describe_operation provides native request schemas', which points at a helper for schema discovery rather than explaining when this tool is the right choice.

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