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

With no annotations, the description carries the full burden and does reasonably well: it discloses a hard cost (0.005 USDC on Base), an alert threshold (<$5,000 USD liquidity), the chains/venues covered, and that it operates on Base Mainnet only. It does not state read-only status, failure behavior for unknown tokens, or rate limits, but the cost and alerting behavior are meaningful disclosures beyond the schema.

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 block, front-loaded with the tool's identity and scope, followed by the risk threshold and cost. No filler sentences, though the all-caps header and run-on structure make it slightly harder to scan than a cleanly separated set of clauses.

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 should ideally indicate what is returned (liquidity figure, per-pool breakdown, alert flag), but it only mentions the alert condition. For a paid, multi-venue analyzer with a 50%-documented schema, the definition leaves the return shape and error behavior unspecified.

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 50%: token_address is documented in the schema, while chain_id (default 8453) is not. The description's 'on Base Mainnet' phrase indirectly explains that chain_id is effectively fixed to Base, adding marginal meaning, but it adds nothing to token_address semantics beyond the schema's own '0x...' description. Baseline 3 for partial coverage with modest compensation.

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 states a specific verb and resource ('Measures verifiable liquidity in USD') and names the exact venues queried (Aerodrome, Uniswap v3/v2, Clanker/Virtuals bonding curves). This clearly separates it from the safety-check siblings, though it never names check_honeypot or rugshield_pre_swap_scan to draw the contrast explicitly.

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 implied via the purpose ('to prevent catastrophic slippage'), suggesting a pre-swap liquidity check, but there is no explicit when-to-use/when-not guidance and no reference to the sibling tools it should be combined with or preferred over. The agent must infer the workflow context.

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