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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: cost ($0.01/call), currency and chain (USDC on Base, eip155:8453), the x402 payment scheme, the exact location of the payment payload (params._meta["x402/payment"]), and the underlying HTTP GET endpoint. That is genuinely useful context an agent cannot get from the schema. It omits return shape, rate limits, and whether unauthenticated/unpaid calls fail or return a 402 challenge.

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 short sentences, front-loaded with the purpose before the payment and transport details. No filler; the density is appropriate for a paid x402 endpoint, though the payment sentence is syntactically dense and could be split for readability.

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 single-optional-parameter read tool with no annotations and no output schema, the description covers access mechanics well but leaves the data contract undefined: no mention of which venues, response fields, or freshness. An agent could pay $0.01 and get an unexpected payload shape without violating anything stated here.

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 0% and the sole parameter 'symbol' is never explained — no format (e.g. BTCUSDT vs BTC), no statement that it is optional, and no hint of what happens when it is omitted (all symbols?). The description does add meaning for the out-of-schema payment meta parameter, which is worth some credit, but the primary filter is left ambiguous.

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 opening phrase 'Multi-venue perpetual funding rates' names the exact resource and scope, which is more specific than most siblings (e.g. fundinglens__rates, funding_rates__funding). It stops short of differentiating itself from those near-duplicate siblings, so an agent cannot tell from the description alone which funding-rate tool to pick.

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 when-to-use guidance at all — no statement of which venues are covered, whether it aggregates or lists, or why one would call this instead of fundinglens__rates or funding_rates__funding. The only 'usage' information is payment mechanics, not selection criteria.

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