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

Beyond readOnlyHint/openWorldHint, it discloses that the tool is stateless, keeps no history, omits lock expiry data, and returns a DROP/DRAIN flag. It also states pricing ($0.002 USDC per successful call via x402 across Base/Solana/Arc) and the billing rule that failed calls are not charged — none of which the annotations convey.

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?

Four sentences, each carrying distinct load — capability, stateless mechanics, exclusions, pricing. The capability statement is front-loaded and no sentence is filler or restatement of the title.

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?

An output schema exists, so return shape needn't be spelled out, yet the description still flags the two most decision-relevant outputs (% change and DROP/DRAIN). With pricing, statelessness, data source and exclusions all covered, an agent can call this correctly without further information.

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 coverage is 100%, so the baseline is 3; the description goes further by explaining the purpose and consequence of previousLiquidityUsd (enables % change and DROP/DRAIN flagging) and by identifying the value as the deepest-pool liquidityUsd from a prior call, which resolves ambiguity the schema description leaves open.

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 verb and resource ('Snapshot of a token's DEX pool liquidity now') and pins down the source and scope (DexScreener, deepest pair plus every pair's USD liquidity). It also explicitly disclaims a neighboring capability ('does not show lock expiry dates'), which cleanly separates it from the liquidity_lock_inspector sibling.

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?

It tells the agent exactly how to get comparative value: pass the liquidityUsd you saved last time as previousLiquidityUsd. It also makes the stateless contract and the fact that no history is kept explicit, so an agent knows what to bring. It stops short of naming sibling tools or stating when to prefer them (e.g. vs. the lock inspector or slippage calculator).

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