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

No annotations are provided, so the description must carry the behavioral burden. It discloses that it's free, includes trial status, and that detail=full adds quota/pass/onboarding, which is useful. However, it never explicitly states the operation is read-only, side-effect-free, or idempotent, nor does it warn about rate limits or token consumption. For a simple manifest retrieval this is acceptable but not fully transparent.

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?

A single, dense sentence that front-loads the critical 'Start here (free)' signal, then lists contents, guidance to siblings, and parameter semantics. Every clause adds value; no fluff. The structure is logical and scannable.

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?

The tool has only 2 parameters, both fully described in the schema, and no output schema. The description explains what the manifest contains (tools, prices, trial status, journeys) and how to adjust detail level. It does not specify the exact return format, but for an overview tool that's a minor omission. Given the simplicity, the description is reasonably complete.

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%: both 'detail' and 'locale' are described. The description adds a small extra semantic by noting 'Compact includes arguments' (the schema only says 'Default compact' without specifying contents). It also reiterates the 'full' behavior, which is redundant. Overall it adds marginal value beyond the schema, but not enough to raise above baseline 3.

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+resource: 'Start here' and 'get_agent_manifest' clearly indicates fetching the manifest of the 4 tools, including prices, trial status, and journeys. It explicitly names the three sibling tools, distinguishing itself as the overview rather than the individual tools. No ambiguity.

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 says 'Start here (free)' which tells the agent this is the entry point, and 'Choose liquidation radar, native BTC/ETH depth or Li.Fi swap' indicates that after retrieving the manifest, the agent should select one of those tools. It does not explicitly say 'use this when you need to decide which tool to use' or exclude cases, but the intent is clear. It lacks explicit alternatives or when-not-to-use guidance beyond the implicit start-here positioning.

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

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

With no annotations provided, the description carries the behavioral burden. It discloses cost, side effects, return object name, and the 'not a trade signal' caveat, plus interpretation rules for output classes. It does not explain authentication or payment flow, but the schema covers that, and the description adds meaningful context.

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 compact with labeled sections, but the middle is a dense run of fragments ('Also magnet, OI, L/S, clusters, real liqs.') that is hard to parse. It is not bloated, but it sacrifices clarity for brevity and does not front-load the core purpose.

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?

There is no output schema, so the description must explain what the agent receives and how to interpret it. It names the return object and some class semantics, but leaves central terms like liq_radar, cluster_grammar, magnet, OI, and L/S undefined. An agent unfamiliar with this domain cannot fully judge whether the tool fits the task.

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 symbol, x_payment, and agent_wallet in detail. The description's whitelist and 'omit=BTC' largely duplicate the symbol enum rather than adding new parameter semantics. Baseline 3 applies.

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 never states a clear verb+resource. It opens with an opaque instruction about cluster_grammar and only later says 'RETURNS: hypernatt_liq_radar_v2.' The 'USE WHEN: terrain / timing / sizing' hint implies the tool provides liquidity terrain data, but an agent would struggle to state confidently what this tool does.

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 usage context with 'USE WHEN: terrain / timing / sizing' and an exclusion with 'NOT a trade signal.' It also advises reading cluster_grammar first when present. However, it does not name sibling alternatives or explain when another tool would be preferable.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it warns that aggregated views see wider price ranges at coarser precision, that volumes should never be summed across views, that there is no strategy signal, no full-book claim, and no fill guarantee. It also discloses the price per call. This is strong added context, though it doesn't detail the exact output shape or pagination.

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-structured: it front-loads the core resource and views, then adds usage warnings, then pricing. Every sentence carries information, though the density of domain-specific terms (REF, M2, M5, AGG4) without expansion slightly reduces accessibility. It earns a 4 rather than 5 because a bit of structural separation (e.g., a sentence on when to use vs. siblings) would improve scannability.

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 read-only market-data tool with no output schema, the description covers the key context: what data is included, the time windows, the aggregation caveat, the companion tools, and the payment method. It doesn't describe the exact response format, but the description's explicit caveats and usage guidance make it complete enough for an agent to invoke correctly. A 5 would require a bit more on the return structure or a clearer when-to-use statement relative to siblings.

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 83%, so the schema already documents most parameters. The description adds semantic context by explaining the lookback window (30s/300s) and the meaning of the four views, which helps an agent understand how quantity_base, side, and symbol relate to the returned data. It doesn't add much beyond the schema for individual parameters, but the baseline is 3 and the description's market-context framing adds value.

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 a specific resource (BTC/ETH perpetual market context) and a specific verb (get/read), and enumerates the four liquidity views (REF, M2, M5, AGG4), size coverage, wall changes, and aggressor flow. It clearly distinguishes itself from siblings by describing a market-data read tool, not a manifest, radar, or swap tool.

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 explicitly says to combine with liquidation radar, read agent_readout and quality first, and warns against adding overlapping volumes in aggregated views. It also states the pricing/payment context (x402 Base/Solana or credits) and the 30s/300s window choice, giving an agent clear when-to-use and how-to-use guidance.

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

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

With no annotations provided, the description fully carries the behavioral burden. It discloses that the MCP call is read-only until the wallet signs, details on-chain gas costs and the 0.5% HyperNatt fee, and notes that Li.Fi may add its own cut, instructing the user to read quote.estimate.feeCosts. It also recommends signing swap_actions_v1 in order, providing clear operational transparency.

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 concise and well-structured, with clear 'USE WHEN:', 'RETURNS:', and 'Side effects:' labels. The opening sentence immediately establishes purpose, and every clause adds relevant information (fees, signing order). There is no wasted text.

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 a complex swap tool with 8 parameters and no output schema, the description covers purpose, usage, return values, fees, and side effects. It could elaborate slightly on what 'execution_readiness' means, but the provided instruction to sign swap_actions_v1 in order gives sufficient operational guidance. Overall, it is highly comprehensive for the tool's complexity.

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 input schema already provides 100% description coverage for all 8 parameters, so the baseline is 3. The description does not add parameter-level details beyond the schema; it focuses on fees and execution flow. It meets the baseline but does not exceed it.

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 explicitly states 'Cross-chain token swap powered by Li.Fi across 70+ chains', providing a specific verb and resource. It also lists concrete use cases (bridge, fund gas, treasury routing, rebalance), clearly differentiating it from sibling tools like get_agent_manifest and get_liq_radar.

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 includes an explicit 'USE WHEN:' section with concrete scenarios (bridge, fund gas, treasury routing, rebalance). This gives clear context for when to invoke the tool, and while it doesn't name alternative tools, the listed use cases are actionable and sufficient for decision-making.

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