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

Annotations already declare readOnly, idempotent, and non-destructive semantics, so the bar is lower. The description adds genuinely useful behavioral detail: results are paged, depth adds order-book move costs, and anomaly/stale flags are included. No contradiction with the 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 description is front-loaded with the core purpose and keeps the alternative routing at the end. The field enumeration adds length but is informative; still, some of it is redundant with the output schema, so it is not maximally concise.

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 description is complete for a read-only, paginated exchange-ticker tool. It covers scope, key parameters, use cases, the sibling alternative, and behavioral details like anomaly/stale flags. Since an output schema exists, the field list does not need to explain return values further.

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 only 50%, so the description must compensate. It adds meaning for depth ('add order-book move costs'), order ('sort'), coin_ids ('narrow to specific assets'), and hints at page via 'paged'. It does not mention include_exchange_logo or fully describe pagination, but it covers most of the gap.

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 clearly states it lists every trading pair listed on one exchange, with a specific scope and verb. It also differentiates itself from get_coingecko_coins_id_tickers by contrasting one-venue coverage with one-coin-across-venues, so an agent can select it correctly.

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 explicitly says to use it to audit one venue's coverage or liquidity, and names the alternative for the opposite use case. This gives an agent a clear decision rule between sibling tools.

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