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

With no annotations, the description does real work: it discloses that the call is paid ($0.005 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged, plus the data source (DefiLlama). What it omits is the mechanics of payment (how the USDC is presented/authorized) and any rate limits, which matter most for a metered endpoint.

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?

Front-loads the cost flag ('Paid.') and then the subject matter, price, access terms, failure policy, and endpoint URL. Dense and well ordered, with only mild redundancy between 'Paid' and the explicit $0.005 line.

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?

Without an output schema, the description does provide what a caller gets back (pools with APY and TVL, aggregating protocols and chains). Pricing and access are covered. The remaining gap is how payment is actually settled at call time, which an agent needs before invoking a paid endpoint.

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 each of the three parameters (sort, limit, min_tvl_usd) is documented with defaults and ranges in the schema itself. The description adds no further parameter meaning, 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?

States a specific resource and result: 'live pools holding STRX across protocols and chains, APY and TVL (DefiLlama data)'. Combined with the tool name this clearly separates it from the chain- and protocol-scoped yield siblings. It is phrased as a topic ('Where to earn yield on STRX') rather than a verb, but the subject matter 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?

Usage is only implied: an agent can infer this is the tool to query when it needs yield venues for STRX specifically. There is no explicit when-to-use/when-not-to-use guidance and no mention of the sibling token tools (e.g. buy_yields_token_usdc) or how to choose between them.

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