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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only a conceptual gloss ('how much leveraged money is committed'), with no information on units, time granularity, snapshot vs. historical behavior, pagination, or auth/rate limits.

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 short sentence that leads with the resource name and resource scope. The trailing clause 'how much leveraged money is committed' is explanatory rather than essential, but the whole description is compact and 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 exists, so the description would need to convey the return shape, units, and whether the value is a single snapshot or history - none of which it does. For a market-data tool with an undocumented parameter and no output contract, this is too thin.

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 single 'symbol' parameter is undocumented in the schema, so the description carries the burden. 'Per symbol' hints that symbol scopes the result, but gives no format example (e.g. BTCUSDT), no case conventions, and does not clarify that symbol is in fact optional given zero required parameters.

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+resource combination ('Open interest per symbol') and adds a plain-language gloss of what the metric means. It is clear what the tool returns, but it draws no distinction from adjacent siblings like get_funding, get_liquidations, or calc_liquidation, leaving the agent to infer the boundary itself.

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 exclusions, and no mention of alternative tools for related derivatives metrics. The only implied usage is 'you want open interest data', which the agent could already guess from the name.

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