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

With no annotations provided, the description carries the full burden and does meaningful work: it discloses that anomalous rates (>1000% APY) and sub-$100K pools are filtered out, and that data is a daily DefiLlama snapshot rather than live. It doesn't state the read-only nature explicitly or any pagination behavior, but the filtering and freshness disclosures are substantive.

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?

Two sentences, zero padding, front-loaded with the search scope before the exclusion rules and data provenance. Every clause earns its place.

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 five-parameter, no-required-arg search tool with no annotations and no output schema, the description covers scope, filters, exclusions, and data freshness. The remaining gap is what a result record contains, which matters somewhat given the absent output schema.

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 schema already documents all five parameters including case-insensitive matching, defaults, max, and TVL clamping. The description restates token/chain/project/min-TVL but adds no syntax or format beyond the schema, so the baseline of 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?

States a specific verb ('Search') and resource ('DeFi Garden's railed pool list') with the filterable dimensions enumerated, so the agent knows exactly what the tool returns. It stops short of explicitly contrasting with the singular-pool siblings (get_pool, get_pool_score), which is the only reason it isn't a 5.

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 usage by enumerating the filter dimensions and stating the two exclusion rules, so it's clear this is the discovery/search entry point. But it never says when to reach for it versus get_pool or get_pool_score, leaving the agent to infer the search-vs-fetch split.

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