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

With no annotations, the description carries the burden well: 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. It omits rate limits and response/pagination shape, 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-loads 'Paid' as the most decision-relevant fact, then data content, then price/payment terms, then endpoint URL. Nearly every clause carries actionable signal and there is no redundant phrasing.

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 read tool with full schema coverage and no output schema, the description covers cost, access, payment rails, and content. The only gap is the shape of returned rows, which an agent must infer from the field list.

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 the meaning of sort, limit, and min_tvl_usd is already documented in the schema. The description adds nothing about parameter behavior (e.g., how min_tvl_usd filters rows), 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?

States a specific verb and resource ('Live DeFi yields for bybit-staked-sol') and enumerates the fields returned (APY, TVL, 7d APY change) along with the data source (DefiLlama). It is not explicitly differentiated from the many sibling per-protocol yield tools, but the protocol-specific name makes the scope 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 context is implied by the protocol-scoped name and the data fields, and payment mechanics are spelled out. However, there is no explicit guidance on when to prefer this over chain-level (buy_yields_chain_*) or token-level yield tools, and no exclusions are stated.

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