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

With no annotations, the description carries the full behavioral burden. It does add useful context: the result is 'latest', 'global', and broken down 'per exchange/symbol'. However, it does not explicitly state that this is a read-only operation, what aggregation window is used, or how the data is sourced. This is minimal but not entirely absent.

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 a single concise sentence that front-loads the key qualifiers: 'Latest', 'global', 'long/short account ratio', and 'per exchange/symbol'. Every word adds meaning and there is no redundant or filler content.

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?

For a zero-parameter tool with an output schema present, the description is mostly sufficient. It communicates the metric, scope, and temporal nature. It could be slightly more explicit about whether the response includes all exchanges/symbols at once, but the output schema likely resolves that.

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 has zero parameters and the schema has 100% coverage, so there are no parameter semantics to document. The description's mention of 'per exchange/symbol' hints at the shape of the response rather than at input parameters. This matches the baseline for a no-parameter tool.

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 identifies the resource (global long/short account ratio) and the scope (per exchange/symbol), and the 'Latest' qualifier adds temporal specificity. It does not explicitly include a verb like 'get', but the tool name supplies that. It does not differentiate from sibling market-data tools, so it stops short of a 5.

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 is given about when to use this tool versus alternatives such as get_funding_rates or get_positioning_regime. The description implies it is used for the latest long/short ratio, but it provides no exclusions, prerequisites, or comparison to sibling tools.

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