long_short_ratio

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

No annotations are provided, so the description carries full burden. It reveals nothing about auth requirements, rate limits, latency, or whether data is historical vs live; only a sample request URL is given. For a data-fetch tool with zero annotation coverage this leaves real gaps.

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 opening clause is duplicated verbatim ('Binance long/short ratios: global account, top-trader account, top-trader position, and taker buy/sell' appears twice), wasting half the description. The example URL is useful, but the restating hurts front-loading.

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, and the description does not describe the shape of the returned ratio data, so an agent can't anticipate the response. Params are covered by the schema and an example is provided, making it minimally adequate for a simple 2-parameter read 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?

Schema description coverage is 100% – both symbol and period are fully documented in the schema, including the period enumeration and the <SYMBOL>USDT mapping. The description's example URL adds usage syntax but no semantic detail beyond the schema, so baseline 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?

States a specific verb/resource: retrieving Binance long/short ratios, and enumerates the four variants (global account, top-trader account, top-trader position, taker buy/sell). Clear what the tool fetches, but no explicit differentiation from siblings beyond the 'companion to funding-oi' note.

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?

No guidance on when to use this versus alternatives like funding_oi, sentiment, or orderbook. The 'Companion to funding-oi' line hints at a pairing but doesn't state a condition or exclusion.

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