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

With no annotations, the description carries the full load, and it does supply genuinely useful operational context: paid access at $0.01/call in USDC on Base, x402 payment placed in params._meta, a free /sample, and the raw HTTP GET endpoint. It does not disclose what the response looks like, error behavior for unsupported symbols, or how 'best' is ranked, so it falls short of a complete behavioral picture for a paid 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-loaded with the resource and scope, then payments and endpoint; nearly every clause carries information. The pricing/URL tail is dense but relevant to actually invoking a paid x402 endpoint.

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?

Sources, normalization, pricing, payment mechanism, and endpoint are all covered, and no output schema exists to explain return values. But the meaning of 'best' and the semantics of `symbols` — the two things an agent most needs to call this correctly — are left unstated.

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% and the single `symbols` parameter is undocumented — no format (comma-separated string vs. multiple values), no indication that it is optional, and no statement of what happens when it is omitted (all symbols?). The description adds no meaning beyond the bare schema.

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 states a specific resource (perpetual funding rates), names the seven venues, and specifies the normalization (8h, annualized). However, it never explains what 'best' selects — presumably the best venue per symbol — which is the tool's defining behavior and its only distinction from fundinglens__rates.

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?

It mentions a free /sample and the per-call price, which hints at a try-before-buy pattern, but gives no explicit when-to-use guidance and never routes the agent to or away from the closely named siblings fundinglens__rates and funding_rates__best.

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