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

With no annotations, the description carries the full behavioral burden. It does add genuinely useful context that structured fields do not contain — that access is metered (5 free calls per signed wallet), implying a signed-wallet auth requirement and a paid fallback — but it says nothing about what is returned, refresh cadence, or which parameter selects the market.

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?

Two short fragments, purpose first, with no filler. The pricing line is arguably promotional, but for an x402 tool the metered-access note carries real information, so the description is efficiently sized overall.

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 tool with two undocumented, ambiguous parameters, no annotations, and no output schema, this description is too thin. It should at minimum disambiguate pair vs symbol and indicate which venues or pairs are supported.

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 two parameters, and the description never mentions 'pair' or 'symbol'. The overlapping semantics of those two names — which one to use, whether both are required, accepted formats like 'BTCUSDT' or 'BTC-PERP' — are left entirely unresolved.

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 the resource ('Perpetual funding rates') but supplies no verb and no differentiation from siblings such as x402-hyperliquid-funding, x402-polyperp-funding, or x402-perp-funding-arb. An agent can infer it retrieves funding rates, but cannot tell which venue/scope this tool covers.

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 statement of when to use this tool versus the several other funding-rate siblings, no prerequisites, and no exclusions. The only context given is a trial/pricing note, which is not usage guidance.

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