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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: source attribution (CCTools public API), a Canton-only scope constraint, and a data-freshness warning about Cantex. It stops short of describing return format or pagination, but with no output schema that gap is minor.

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?

Front-loaded with the core purpose and fields, then the disambiguation. The Cantex parenthetical is a touch wordy and slightly interrupts the routing sentence, but every clause carries real information (coverage gap, staleness reason). No filler.

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, no-output-schema pool query the description covers purpose, fields returned, source, scope, coverage caveat, and the alternative tool. Without an output schema, more detail on the response shape would help, but the field enumeration partially compensates. Nothing essential to correct invocation is missing.

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% and the single enum parameter is fully documented ('Restrict to one DEX. Omit for all three.'). The description's listing of OneSwap, Send, and Tradecraft mirrors the enum values without adding syntax or default behavior beyond what the schema already states, so the 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?

Specific verb+resource ('Get per-pool DeFi liquidity data') with named fields (pair, TVL, fee rate, APY, reserves), named sources (OneSwap, Send, Tradecraft), and explicit sibling differentiation from get_token_market (pool-level vs aggregate protocol-level). An agent can distinguish this from get_token_market without opening either schema.

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?

Explicitly routes the agent: use this for pool-level detail, use get_token_market for aggregate protocol-level TVL. It even explains why the alternative differs (Cantex coverage) and flags a caveat (Cantex API down, numbers marked stale). When-to-use and when-to-use-the-other are both stated.

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