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

Beyond the annotations, it discloses cost and rail ($0.003/call via x402, USDC on Base only), that failed calls are not charged on Base, that a bad symbol returns 400, the 5-minute data staleness, and buyer terms. For a paid tool this is exactly the extra context annotations cannot carry.

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?

It leads with what the tool returns and what the output looks like, which is the right order. The payment and legal-terms material is dense but relevant for a paid tool, though the disclaimer and terms sentences could be tightened.

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, describing the returned fields (instId, fundingRate, fundingTime, crowding hint with sides and levels) and the error/billing behavior covers nearly everything needed to call it. The remaining gap is the symbol parameter that the description promises but the schema does not define.

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 input schema declares zero properties, yet the description says a single coin can be requested via 'symbol=', a parameter that exists nowhere in the schema. The high schema coverage is vacuous with no parameters, so the description's invented parameter creates a concrete risk of malformed calls rather than adding accurate semantics.

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 states a specific verb and resource: current OKX USDT-swap perpetual funding rates for BTC, ETH and SOL, with an optional single-coin mode. That is far more specific than the bare name 'funding', but it never names a sibling (funding_report, funding_reports, market_quote) to say how this differs from the report-style tools.

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 clear usage boundaries: coverage is limited to BTC/ETH/SOL, and data refreshes roughly every 5 minutes so calling more often returns identical values. It stops short of naming an alternative tool or an explicit 'do not use this for historical/multi-asset series' exclusion.

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