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

With no annotations, the description carries the full burden and does add genuine context: it declares the operation read-only, warns that 'positions, trades, and returns are not verified', and discloses a per-call cost ($0.10 via x402). However, it says nothing about what a 'verdict' contains, latency, or how tracked markets are defined, leaving notable behavioral gaps.

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 tight sentences with no waste: purpose first, then the verification caveat, then pricing. The information is front-loaded and each sentence earns its place, though the cost clause could arguably be trimmed in favor of usage guidance.

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?

With no annotations and no output schema, the description is the only source of truth, and it partially covers the ground by naming the returned components (basis, 24h sample context) and disclaiming verification. It still omits return shape/structure and any routing distinction from the three sibling tools, so it is adequate but incomplete.

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 tool takes zero parameters (empty schema), so there are no parameter semantics to explain and the baseline is 4. The description correctly does not invent parameters or claim configurability.

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?

States a specific verb and resource ('Read-only Hyperliquid funding verdicts') plus scope ('tracked markets'), so an agent knows it retrieves funding verdict data. It does not explicitly differentiate itself from siblings like carry_opportunities or carry_digest, though the 'verdicts' framing implies a distinct output.

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?

No when-to-use guidance, no exclusions, and no direction toward alternatives such as carry_free_sample or carry_opportunities. The 'tracked markets' scope is implied but there is nothing telling the agent when this tool is the right choice over its three siblings.

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