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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value beyond them: the call is free (no credit cost), the data is sourced from four named venues, and funding is reported both per-8-hour and annualised. It does not say what happens if a coin is not listed on all venues or whether requests are rate limited.

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 short sentences with no filler; the scope and data types are front-loaded. The fragment 'Free.' is abrupt but does carry the cost signal, so nothing is wasted.

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 one-parameter read-only tool with no output schema, the description covers what is returned (funding per 8h and annualised, open interest), the granularity, and the data sources, which is close to sufficient. It leaves return shape (per-venue rows) and unavailable-data behavior unstated, which are minor gaps.

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 coverage is 100% and the single 'coin' parameter is documented with examples (BTC, ETH, SOL), so the schema does the heavy lifting. The description only restates that the input is a crypto coin and adds the venue context, which is the expected baseline of 3 for full schema coverage.

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 names the exact data (funding per 8 hours and annualised, plus open interest), the exact scope (a single crypto coin), and the exact venues (Hyperliquid, Bybit, OKX, Binance). No sibling tool covers funding/OI data, so an agent can distinguish it immediately.

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 gives no when-to-use guidance, no prerequisites, and names no alternatives among siblings such as trade_conditions or risk_check. The 'Free' tag hints at a cost advantage but never states when this tool should be selected over anything else.

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