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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and mutability profile is fully covered. The description adds nothing beyond that — no rate limits, no note on whether results are a full snapshot, and no interaction with the page/limit paging behavior that would contradict 'all supported'.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently sized, though arguably so terse that it leaves the tool's scope entirely to inference.

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 low-complexity listing tool with full schema coverage and no output schema, the definition is minimally sufficient to call correctly. It leaves the shape of a returned pair and the pagination-vs-'all' tension unexplained, which is a modest but real gap.

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%, with page, limit and currency all documented in the schema including defaults and bounds, so the baseline of 3 applies. The description contributes no additional parameter meaning (e.g. what 'currency name' format is expected).

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 (List) and resource (supported flash swap currency pairs), and the 'flash swap' qualifier distinguishes it from the near-identical siblings cex_spot_list_currency_pairs and cex_margin_list_uni_currency_pairs. It stops short of naming those alternatives, so an agent must infer the domain split from names alone.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer this over the spot/margin pair-listing siblings. The description is a bare capability statement with zero routing information.

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