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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description need not repeat. However, it adds no behavioral context beyond the annotations, such as whether data is real-time or delayed, or any rate limits.

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 only 5 words, which is extremely concise. While brevity is valued, it sacrifices informativeness. A few more sentences to explain what 'pool data' includes would improve usability without being verbose.

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?

Despite having a good input schema and annotations, the description fails to explain what the output contains (e.g., pool addresses, liquidity amounts, token pairs). An output schema exists, but the description should still set expectations. For a tool with 4 optional parameters, more context is needed.

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 has 100% description coverage with clear descriptions for query, network, sort_by, and limit. The tool description does not add extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 'Get DEX liquidity pool data' is a clear verb+resource, but it is too generic to distinguish from many crypto sibling tools like crypto.coin.detail or crypto.market.overview. It lacks specificity about what pool data entails (e.g., reserves, prices, volume).

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 provides no guidance on when to use this tool versus alternatives. Given many crypto-related sibling tools, explicit differentiation (e.g., 'Use for liquidity pools, not token prices') is missing.

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