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

With no annotations provided, the description carries the behavioral transparency burden and does meaningful work: it discloses that data is 'cached,' that it is refreshed every 15 minutes, and that the call 'Returns' data rather than mutating state. This gives the agent a clear read-only mental model. It does leave 'registry enrichment' and the meaning of 'top' somewhat undefined, but the core behavior is transparent.

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 sentences, each serving a distinct purpose: core operation, filter options, and returned data plus freshness. The main purpose is front-loaded and there is no filler or redundancy.

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 query tool with 8 optional parameters and no output schema, the description covers purpose, filters, return fields, and data freshness. It does not explain pagination behavior or whether filters combine, but the schema documents defaults, limits, and enums, so the agent has enough to invoke the tool correctly.

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 already documents all 8 parameters with descriptions and enums, so the baseline is 3. The description adds useful examples for protocol, chain, and token filters, and the return metrics (TVL, APY, volume) map naturally to the sortBy enum. However, it does not add meaning beyond the schema for pool, limit, offset, order, or sortBy.

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 opens with a specific verb and resource: 'Get a cached snapshot of top DeFi liquidity pools.' It also lists the available filters and the key returned metrics, making the tool's scope clear. It does not explicitly distinguish itself from sibling tools, but the pool-specific focus and return fields separate it from the token- and transaction-oriented siblings.

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 implies the tool is for querying current pool snapshots and filtering by protocol, chain, or token, but it provides no explicit when-to-use or when-not-to-use guidance. It never mentions alternatives or contrasts with sibling tools such as token_research, registry_lookup, or token_intel, leaving routing decisions to the agent.

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