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

With no annotations supplied, the description does real work: it discloses the cost ($0.005 USDC), payment chains (Base or Solana), absence of account/API-key requirements, failure-billing policy (failed calls not charged), and the upstream data source (DefiLlama). Gaps remain around rate limits and response/pagination shape, but the core commercial and auth behavior is well covered.

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 front-loaded with 'Paid.' and the core value statement, then pricing, then URL, with essentially no wasted words. It is dense but reads cleanly; the only minor issue is that the value proposition and pricing run together in a single long sentence.

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 zero-required-parameter, three-optional-parameter read tool with no output schema and no annotations, the description covers purpose, returned metrics, cost, payment, and auth. The remaining ambiguity is how payment is actually executed (only a bare URL is given) and the response envelope, which keeps it short of full completeness.

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 with defaults in the input schema. The description adds no syntax or format detail beyond that, which meets the baseline but does not exceed it.

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 verb and resource: live DeFi yields for the venus-core-pool protocol, covering its pools across chains with APY, TVL, and 7d APY change. The protocol name in the description lets an agent separate it from the buy_yields_chain_* and buy_yields_token_* siblings, though it never explicitly contrasts itself with them.

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?

The description makes clear this is a paid, credential-free call with the price and payment chains, which is useful context for deciding whether to invoke. However, it gives no explicit guidance on when to prefer this protocol-level tool over the sibling chain-, token-, or top-level yield tools, leaving the agent to infer the choice from the name.

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