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

Goes well beyond the annotations by disclosing the per-call cost ($0.005 USDC on Solana), the x402 payment handshake (call unpaid to receive a PaymentRequired challenge, then retry with payment at _meta["x402/payment"]), and an HTTP equivalent endpoint. These are exactly the operational facts an agent needs before invoking a pay-per-call tool.

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?

Front-loads purpose, then cost/payment mechanics, then an HTTP fallback, with each segment doing work. The x402 retry instruction is dense but necessary; no sentence is pure 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?

Covers purpose, price, payment flow, and an alternate transport, which is strong for a tool with no output schema. It stops short of indicating which three venues are covered or what shape the returned funding data takes.

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 schema already documents the flexible symbol format, so the description's main addition is showing {symbol} as a URL path component. That is a marginal gain over the structured schema, consistent with the baseline 3.

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 concrete verb and resource: 'Fetch funding rates across three perp venues.' An agent can tell this returns aggregated perp funding data. It doesn't differentiate itself from the sibling funding_liquidations, which is a related but distinct funding-domain tool.

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?

Usage is implied by the description (get funding rates for a symbol), but there is no explicit when/when-not guidance or routing to a sibling like funding_liquidations. The payment procedure is spelled out, which is operational rather than selection guidance.

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