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

With no annotations, the description carries the full burden and does well: it discloses that calls are paid ($0.01 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and that data comes from DefiLlama. It omits rate limits, response shape, and whether results are cached, which keeps it below 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?

Front-loaded with the core purpose and then the commercial terms in short clauses; every sentence earns its place except the raw endpoint URL, which is marginally useful for debugging but not for tool selection.

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, the description covers the returned fields, the data source, the payment mechanics, and the endpoint. An agent has everything needed to decide to call it and to anticipate the cost.

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 documented in the schema. The description adds nothing about defaults, interaction between filters, or sort ordering, so 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 the specific resource (the-vault-liquid-staking) and states exactly what is returned: its pools across chains with APY, TVL, and 7d APY change from DefiLlama. That clearly separates it from the chain-scoped and token-scoped siblings, though it never explicitly says 'use buy_yields_chain_X for chain-level views'.

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 by the protocol scoping; there is no explicit statement of when to pick this over buy_yields_chain_base or buy_yields_token_usdc. The commercial context (paid, $0.01, no key) is present but that is not selection guidance.

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