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

With no annotations, the description carries the full burden and does add meaningful behavior: it states the output includes 30d mean, volatility, IL risk, and forecast, and discloses that results are signed, timestamped, and cost $0.002 per call. It does not mention output shape or more detailed semantics of 'forecast' or 'IL risk', but it offers solid transparency beyond a bare purpose statement.

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 compact, front-loads the main purpose, and uses a separate sentence for signature/timestamp and cost. It is not verbose, but terms like 'IL risk' and 'forecast' are left undefined, which slightly reduces clarity.

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 tool with seven optional parameters, no output schema, and no annotations, the description gives a reasonable overview of returned metrics and filters but leaves important details unstated, such as the output structure, sort direction beyond 'Top', interpretation of forecast, and any access or rate-limit requirements. It is adequate but has clear gaps.

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 echoes filters like chain, project, stablecoin, and TVL but adds essentially no meaning beyond the schema's own parameter descriptions, and it omits mention of limit, symbol, and maxSigma even though those are documented in the schema.

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 clearly defines the tool as returning top DeFi pools ranked by APY with supporting metrics and filters, so an agent can understand its core function. It does not explicitly contrast with the sibling defi_yield_movers, so it falls short of full sibling differentiation.

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 intended use is implied: call this to get top-yielding DeFi pools with various filters. However, there is no explicit guidance about when to prefer this over defi_yield_movers, stablecoin_peg_monitor, or other siblings, and no when-not-to-use conditions are provided.

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