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

With no annotations, the description carries the full burden and does substantial work: it discloses that the call is paid ($0.002 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged — precisely the commercial/auth behavior an agent must know before invoking. It omits rate limits, response envelope shape, and what happens on insufficient funds, keeping it short of a 5.

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 content is front-loaded and dense — scope first, then returned fields, then price/payment, then the endpoint URL — with no filler sentences. The telegraphic style is efficient, though the price and URL tail could be considered boilerplate relative to the core purpose.

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 read-only data tool with no output schema, the description adequately previews the returned fields (base/reward APY, TVL, 7d change) and covers payment, auth and failure charging. Missing pagination/response-size behavior and rate limits are minor for a 3-optional-parameter endpoint query.

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, limit and min_tvl_usd are already fully documented with defaults. The description reinforces the sort dimension ("by TVL or APY") and lists the returned metrics, but adds no syntax or format detail beyond the schema; 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 names a specific resource and scope: "Live DeFi yields on Stacks: top pools by TVL or APY" with base/reward APY, TVL and 7d APY change sourced from DefiLlama. The chain scoping distinguishes it from the many buy_yields_chain_* and buy_yields_protocol_* siblings, though it never explicitly routes the agent to those alternatives.

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 implied by the stated output (top pools ranked by TVL or APY) and the price/payment terms, so an agent can infer when the data is relevant. However, there is no explicit when-to-use or when-not-to-use guidance versus buy_tvl_stacks or the protocol- and token-level yield siblings, which is a real gap in a family of hundreds of tools.

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