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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered; the description's added value is the freshness/scope claim ("live open interest right now") and the fact that coverage is all venues. It does not disclose response size, pagination, or how stale "right now" is, which matters for an all-venues enumeration that could be large. Adds some context beyond annotations but leaves the operational profile thin.

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?

Two sentences, dense and front-loaded: scope first, then the routing instruction. Minor noise from the bracketed "[measured]" tag and the unexplained "(BASEUSDT symbols)" parenthetical, but nothing meaningfully wasteful.

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 no output schema, the description must carry the return-value burden, and it does enumerate the contents (venues, per-venue live-OI contracts, top-100 coin pool). It omits the actual response shape (field names, nesting, ordering) and any size guidance, which is the main residual gap for a zero-param discovery tool.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly does not waste words on inputs.

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?

Names the resource precisely: every tracked venue plus, per venue, the contracts with live open interest (BASEUSDT symbols), plus a top-100 coin pool. That is a concrete verb-implied enumeration of markets, distinguishable from data-fetching siblings like get_open_interest or get_hip3_markets. It stops short of explicitly contrasting with the other market-listing siblings (get_hl_builder_markets, get_hip3_markets, get_stocks), so it is clear but not fully sibling-differentiated.

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?

"Call this first when unsure which symbol or exchange string another tool accepts" is an explicit, actionable usage trigger that ties this tool to the rest of the toolset as a discovery step. There are no stated exclusions (e.g., when to prefer get_hip3_markets for HIP-3 venues), so it gives clear context but not a full routing matrix.

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