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

With no annotations, the description must carry the behavioral disclosure burden. It helpfully lists the returned data and frames the tool as an execution-cost preflight, but it does not disclose data freshness, slippage estimation assumptions, or explicit read-only/no-side-effect behavior. 'Get' implies a query, yet important caveats are left implicit.

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?

Three tight sentences cover action + resource, returned fields, and use case. There is no filler, and the identifying information is front-loaded.

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 simple optional-parameter query with full schema coverage, the definition is mostly complete: it names the chain, target tokens, returned metrics, and an explicit use case. It loses a point because it does not clarify how this differs from tokenintel_dex_depth, which could be relevant given the sibling set.

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 baseline is 3. The description adds no parameter-specific meaning beyond 'token' and 'limit'; it mentions outputs but not how either parameter affects them beyond what the schema already states.

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 action and resource: get on-chain DEX liquidity data for fan tokens on Chiliz Chain. It also lists the concrete outputs (TVL, depth, reserves, estimated slippage), which makes the purpose unmistakable. It does not explicitly distinguish itself from the similarly named sibling tokenintel_dex_depth.

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 provides a clear use context: 'Critical for agents that want to understand execution costs before trading on-chain.' However, it does not name alternatives or state when not to use this tool, so it stops short of full routing guidance.

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