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

No annotations are supplied, so the description carries the full burden, yet it says nothing about read-only vs mutating behavior, cost/payment requirements (the x402 prefix implies paid calls), rate limits, or freshness of the history window. It also gives no hint about the shape of the returned curve or how many venues are covered.

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?

One compact sentence with the differentiating capability placed immediately after the tool name; nothing is redundant. It is arguably too terse rather than padded, but structurally it is front-loaded and clean.

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 five-parameter tool with no annotations, no output schema, and no parameter descriptions, the definition is far too thin. An agent cannot determine what to pass for asset, limit, or the alert/spread thresholds, nor what the response contains, from this description alone.

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?

All five parameters (asset, limit, historyDays, alertAnnualPct, minAnnualSpreadPct) have 0% schema description coverage, and the description explains none of them. At best 'per-venue history curve' faintly gestures at historyDays, but units, formats (all params are typed as strings), defaults, and the meaning of the two threshold parameters are entirely undocumented.

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 identifies the resource as a cross-venue perpetual-futures funding radar and adds that this variant also returns a per-venue history curve, which distinguishes it from the sibling x402-perp-funding-radar. However, 'radar' is jargon rather than a concrete verb+resource, and the sentence defers to an unnamed 'same' tool for the core behavior, so an agent must infer that it compares funding rates across exchanges.

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 only implied: the 'deep' suffix and the 'plus a per-venue history curve' clause suggest selecting this tool when historical funding data is needed rather than the plain radar. There is no explicit statement of when to prefer it over x402-perp-funding-radar, x402-perp-funding-arb, or the various x402-hyperliquid-* / x402-polyperp-* funding siblings.

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