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

With no annotations, the description carries the full burden and does a fair job: it discloses the $0.002 USDC price, payable on Base or Solana, that no account or API key is required, and that failed calls are not charged. It omits rate limits, latency, and what a response looks like beyond the listed fields, so meaningful gaps remain for a paid 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-loaded with 'Paid.' so the cost signal lands first, then scope, then fields, then payment mechanics and the URL. Every clause carries information; the only mild bloat is the redundant 'No account, no API key' pairing.

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 paid read with no output schema, the description covers what matters: data fields returned, source, price, payment chain, and failure charging policy. It stops short of describing response shape or pagination behavior for the limit parameter, but nothing essential to calling it is missing.

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%, with sort, limit, and min_tvl_usd each documented including defaults and ranges, so the schema does the heavy lifting. The description adds no filtering or sorting semantics beyond noting that APY and TVL are part of each row, which is the correct baseline for high-coverage schemas.

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 jito-liquid-staking protocol, with named fields (APY, TVL, 7d APY change) and the data source (DefiLlama). The protocol-scoped name plus description separates it from the chain-scoped and token-scoped siblings, though it never explicitly contrasts itself with buy_yields_token_jitosol.

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 tool's scope - query yields for this one protocol - and the paid nature is front-loaded so an agent knows when cost applies. There is no explicit statement of when to prefer buy_yields_chain_* or buy_yields_token_jitosol instead, so sibling routing is left to inference.

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