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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-dependency profile are covered. The description adds that the data is 'live' and sourced from OKX, which is useful freshness/provenance context, but it says nothing about rate limits, caching, or behavior when the symbol is unknown.

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?

Two tight sentences: the first front-loads the resource and the returned fields, the second gives the usage trigger. No filler or redundancy.

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 single-parameter read tool with no output schema, the description compensates by listing the four returned metrics, so an agent knows what it gets back. Combined with annotations covering the read-only/open-world profile, nothing material is missing.

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% and the single 'symbol' parameter is documented with format examples (BTC, ETH, SOL). The description only reinforces 'one crypto asset' and does not add syntax, casing, or pair-format guidance beyond 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?

States a specific verb (get) and resource (live perpetual-futures derivatives from OKX) and enumerates the exact metrics returned: funding rate, open interest, long-account %, last price. This is distinguishable from siblings like get_market_overview or get_market_state, which cover different scope.

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?

Explicitly states when to use it: 'Use when the user asks about funding, open interest, positioning, or the perp price of a specific coin.' That is a clear triggering context with concrete query topics, though it names no alternatives or when-not conditions (e.g., spot price vs perp price).

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