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 well: it discloses pricing ($0.01 USDC on Base or Solana), payment rails, that no account or API key is required, that failed calls are not charged, and that the underlying data is DefiLlama-sourced. It stops short of stating rate limits, caching/freshness cadence beyond 'Live', or pagination behavior.

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?

Very compact and front-loaded, with the 'Paid.' marker first so the cost signal is not buried, followed by what the data is, then payment mechanics. The trailing raw URL is the only element of questionable value to an agent already given the tool binding, but it is short and harmless.

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 3-optional-parameter read tool with no output schema and no annotations, the description covers cost, auth, failure handling, data provenance and the returned metrics, which is nearly everything an agent needs to call it correctly. The main remaining gap is the concrete response shape (field names, row structure) and any rate-limit constraints.

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 sort (tvl/apy), limit (1-100, default 20) and min_tvl_usd (default 100000) are already documented in the schema. The description adds no extra meaning about how these interact or what units/format the returned rows use, so the baseline 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?

The description gives a concrete verb and resource: live DeFi yield pools for the orca-dex protocol, with the specific metrics returned (APY, TVL, 7d APY change) and the data source (DefiLlama). The protocol name is duplicated from the tool name rather than contrasted against siblings like buy_yields_chain_* or buy_yields_token_*, so differentiation is implicit rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The payment and auth notes ($0.01 USDC, no API key, no charge on failure) help an agent judge cost but do not tell it when this protocol-level yield feed is the right choice over a chain-level or token-level yield tool.

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