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

Annotations already convey readOnly, idempotent, openWorld, and non-destructive behavior, so the description need not repeat those. It adds meaningful context about the specific outputs (open interest per venue, funding, 1h/24h change, crowded flag), but does not disclose additional behavioral traits such as data freshness, pagination, or how the spot flow component is calculated.

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 dense sentence that front-loads the resource and quickly enumerates supported examples and returned data. It is efficient despite being long, and every clause contributes information; a slight restructure could make it easier to parse quickly.

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 reasonably carries the burden of describing return values, and it lists the key fields: open interest long/short, funding, 1h/24h change, and crowded flag. It also clarifies the supported asset universe and venues. However, the phrase 'next to the spot flow' is left vague and some output formatting details are absent.

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 covers 100% of parameters and already gives examples like TSLA and XAUUSD for the symbol. The description adds more symbol examples and venue names, but this is marginal added meaning beyond the schema and does not substantially improve an agent's understanding of the parameter's format or constraints.

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 states the resource (perpetual futures positioning for tokenized stocks, ETFs, commodities) and what data it returns, including open interest, funding, changes, and a crowded flag. It is specific and informative, though it does not explicitly differentiate itself from sibling tools like get_market_intelligence or get_symbol_intelligence.

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?

The description implies usage via the data it returns, but it does not explicitly state when to use this tool versus alternatives, nor does it mention conditions where a different tool would be more appropriate. With many get_* siblings, more guidance would help disambiguation.

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