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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context by detailing the returned values: current Binance funding rates, cross-exchange average per 8 hours, open interest in USD with 24-hour and 1-hour changes, Binance long-account share, long/short ratio, and top-trader positioning. It does not discuss rate limits or error behavior, but the output semantics are well covered.

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 front-loaded with purpose, then usage examples, then return details. Although the final sentence is dense, every part provides useful information not found in the schema and there is no filler.

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?

Given the simple one-parameter schema, the absence of an output schema, and the read-only annotations, the description is complete enough for an agent to select and invoke the tool correctly. It explains the scope, use cases, and returns in sufficient detail.

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 schema already documents the single parameter at 100% coverage, including the coin symbol and the default to the top ten. The description adds useful context by specifying that the top ten are ranked by open interest and gives an example coin, but this is incremental over the schema.

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 and metrics: funding rates, open interest, and long/short ratio for perpetual futures, scoped to one coin or the ten largest. It distinguishes itself implicitly from the sibling tools (which cover sentiment and liquidations) but does not explicitly name or contrast those alternatives.

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?

It gives concrete example questions that show when to use the tool and explains the two coverage modes (single coin or top ten by open interest). It does not name alternative tools or exclusion cases, but the intended use is clear.

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