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

With no annotations, the description supplies valuable operational behavior: the call is paid, costs $0.005 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. It also identifies the data as live and DefiLlama-sourced, though it does not explicitly confirm read-only behavior or discuss freshness and 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 compact and front-loaded, leading with its paid nature and data purpose before giving price, access requirements, failure billing, and endpoint URL. Each short statement contributes useful selection or invocation information without filler.

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 lookup with three optional controls, it covers the resource, scope, principal data fields, source, cost, payment networks, authentication needs, failure billing, and URL, while the schema covers invocation controls. Explicit sibling-selection guidance and slightly more detail about result rows would help, particularly because there is no 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 coverage is 100%, and the schema already documents all three optional parameters, including sort choices, the limit range, and defaults. The description adds no parameter syntax, interactions, or filtering examples beyond that structured information, so the baseline score 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?

The description clearly identifies the resource and scope: Fluid DEX pools across chains, with APY, TVL, and 7-day APY change from DefiLlama. It lacks an explicit retrieval verb and does not distinguish itself from related Fluid protocol or chain/token yield siblings, but the core purpose is unambiguous.

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 case: obtaining current yield data specifically for fluid-dex pools across chains. It does not explain when to choose buy_yields_chain_*, buy_yields_token_*, buy_yields_top, or other protocol variants instead, so alternative-based routing is absent.

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