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

With no annotations, the description covers key behavioral traits: cost per call, venue inclusion/exclusion logic, that Hyperliquid is always present, ordering, and data fields. It does not mention rate limits or authentication, but the x402 cost indicates payment.

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?

The description is dense but informative, listing all returned fields. It is slightly long but every sentence adds value. Could be improved with bullet points 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?

Given the complexity of multiple venues and many fields, the description sufficiently explains what is returned and includes important context like cost and omission logic. However, it does not clarify whether results cover multiple coins or a single coin; it implies multiple but could be more explicit.

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?

The schema already describes the single parameter 'limit' with default and max. The description adds no additional meaning or context for this parameter, so it scores at the baseline of 3 for 100% schema coverage.

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 clearly states it provides live cross-venue perpetual-futures funding rates from specific exchanges, listing fields and ranking by volume. However, it does not explicitly differentiate from the sibling 'crypto_funding_preview', which likely provides a sample.

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?

The description implies usage for live full-rate data but does not explicitly state when to use this tool versus the preview sibling or other tools. No guidance on prerequisites or exclusions.

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