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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description goes further by disclosing the full content of the response (OI in coins and USD, market share, 1h/4h/24h change and USD flow, OI/volume ratio, totals) in the absence of an output schema. It does not state data freshness, which venues are covered, or sort order, so it stops short of a 5.

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 that leads with the tool's essential scope before listing returned metrics. The metric list is dense but each item earns its place because there is no output schema; only the duplicated BTCUSDT example borders on redundant with the schema.

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?

With one required parameter and no output schema, the description carries the return-value burden and does so thoroughly, enumerating every metric and the market-total rollup. Gaps are secondary: venue coverage, sort direction, and whether figures are real-time or snapshotted are unstated.

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 coverage is 100% and the schema description already defines the BASEUSDT format and the 1000PEPE/kPEPE folding rule. The description only repeats the BTCUSDT example, adding no new meaning about normalization, casing, or invalid-symbol behavior, so the baseline of 3 applies.

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 gives a specific resource (open interest) with an explicit scope modifier, 'per-venue ranking', which separates it from the aggregate siblings get_open_interest and get_open_interest_history. It then enumerates the measures returned, so an agent knows this is a cross-exchange comparison table rather than a time series or single-market snapshot, though it never names those siblings directly.

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?

Usage is only implied: the phrase 'per-venue ranking' and 'plus market totals' suggest it is the right call when comparing exchanges rather than tracking one venue over time. There is no explicit when-to-use/when-not, no mention of get_open_interest or get_open_interest_history as alternatives, and no stated prerequisite (e.g. that the symbol must be a listed perp).

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