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

With no annotations present, the description does carry important operational behavior: this is a paid call ($0.01 USDC on Base, eip155:8453) settled via x402 in params._meta, plus the HTTP route. It discloses nothing about read-only semantics, rate limits, error handling, or whether ranking favors highest net return.

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: outputs first, then price, then transport. The payment/pricing sentence is load-bearing information rather than filler. Minor waste in the redundant full URL plus 'HTTP: GET' framing.

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?

Because there is no output schema, listing the returned metrics is genuinely useful and covers the return shape. However, key inputs (symbols format, hold_days default) and the ranking/payment-failure behavior are missing for a 2-parameter paid tool.

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 0% for both parameters. The phrase 'over a holding period' loosely maps to hold_days but gives no units, default, or bounds, and symbols is entirely unexplained (no format, delimiter, or which venues/symbols are accepted). The description does not compensate for the coverage gap.

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 a specific operation (ranked cross-venue funding carry) and enumerates the returned metrics (gross annualized gap, bps/day, round-trip fee, breakeven days, net return). This is enough to distinguish it from siblings like funding_rates__funding and funding_rates__spread, though it never names those siblings explicitly.

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 guidance on when to pick this over funding_rates__spread, fundinglens__best or fundinglens__rates, which appear to overlap in intent. The payment sentence explains cost but not selection criteria, so the agent must infer usage from the title alone.

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