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

With zero annotations, the description carries the full burden and does disclose the highest-value behavioral facts: this is a paid call at $0.01 USDC on Base (eip155:8453), payment travels in params._meta["x402/payment"], and a free /preflight sample exists — all material auth/cost context an agent must know before invoking. It falls short of 5 because it says nothing about failure modes (unknown symbol, upstream exchange outage) or rate limits.

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?

Three tight sentences, front-loaded with what the tool returns and where the data comes from, followed by the commercial/payment terms and the raw endpoint. Nothing is repeated and no sentence is 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?

For a one-parameter read tool with no annotations and no output schema, the description covers cost, payment mechanism, data source and endpoint, which is a lot. The remaining gap is the return payload: 'annualized carry' is named but not characterized (per-exchange rows? a single aggregate?), and on a paid call an agent benefits from knowing roughly what it is buying.

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% for the single `symbol` parameter, so the baseline is already high. The description adds modest value beyond the schema by enumerating supported assets ('BTC, ETH, SOL and more'), which tells the agent the symbol vocabulary is a known asset ticker rather than an arbitrary string or pair like BTCUSDT.

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+resource: perpetual-futures funding rates plus annualized carry, sourced from exchange public market-data APIs, in a single call. It does not, however, differentiate itself from the many siblings in the same family (funding_rates__batch, __best, __history, __rates, fundinglens__rates), so an agent cannot tell from the description alone why it would pick this single-symbol variant over the others.

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?

There is no explicit when-to-use or when-not-to-use guidance, and the siblings are never named. The 'Free /preflight sample' line implies a trial path but does not say under what conditions an agent should take it versus paying for a call.

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