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

No annotations are provided, so the description carries the burden. It discloses cost ($0.001 x402), payment rails (Base or Solana), return object type, and explicitly 'Side effects: none'. It also tells the agent how to interpret the data class, which is useful behavioral context beyond what annotations would cover. It does not describe the 402-retry flow, but that is covered in the x_payment parameter description.

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 well-labeled with USE WHEN, NOT, RETURNS, COST, and Side effects, making key decision points easy to locate. The sequencing instruction is front-loaded, and no sentence is wasted even though the tone is terse and jargon-heavy.

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 low-parameter, read-only style tool with no output schema, the description gives enough: return type, cost, payment rails, context records, and side effects. It does not fully define the structure of hypernatt_liq_radar_v2 or clarify what happens on payment denial, but those are partially inferred from x_payment schema.

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 100%, so the schema already documents all three parameters. The description adds minimal new parameter semantics: it repeats the strong whitelist and default BTC behavior already stated in the symbol schema, and mentions x402 rails already covered. It argues domain interpretation of output data, but doesn't materially enrich parameter meaning.

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 positions the tool as a liquidity-radar data reader: it returns hypernatt_liq_radar_v2, focuses on magnet, OI, L/S, clusters, real liqs, and frames its role as terrain/timing/sizing rather than trade execution. This distinct from the sibling swap_via_nattswap and get_agent_manifest. However, the purpose is never stated in a plain 'Gets liquidity data' style and relies on domain jargon, so it is not a 5.

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 gives explicit when-to-use ('USE WHEN: terrain / timing / sizing') and when-not-to-use ('NOT a trade signal') guidance, and even prescribes a sequence ('If cluster_grammar is present, read it before liq_radar'). It does not name a specific alternative tool for trade execution, so it stops short of fully explicit alternatives.

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