Crypto staking and interest yields

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

With no annotations, the description carries the behavioral transparency burden. It adds useful context about the risk-adjustment method (TVL, base vs emission share) and the A/B/C rating scale, which sets expectations about output. However, it omits data sources, update frequency, and any access or rate limitations, leaving notable gaps.

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 a single long sentence that front-loads the core purpose ('Where to earn interest or staking rewards') and then packs in categories, risk-adjustment details, and ratings. Each clause adds value, though splitting it into two sentences would improve readability.

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?

Given there is no output schema and no parameters, the description provides a solid overview: yield types, platforms, risk-adjustment metrics, and rating scale. It does not detail the exact return format beyond ratings, but for a no-param research tool, it is adequately complete.

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?

The input schema has zero parameters, so schema coverage is trivially 100% and the baseline is 4. The description does not need to explain parameters; it provides enough context about the tool's scope and methodology to make the lack of parameters obvious.

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 clearly states the tool's purpose: finding where to earn interest or staking rewards on crypto and stablecoins. It enumerates specific categories (DeFi staking APY, stablecoin lending, liquidity-pool yields) and platforms (CeFi/DeFi), and the A/B/C rating system distinguishes it from generic crypto research tools like sibling crypto_research.

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 implies usage: use when you want to compare crypto yield opportunities. However, it does not explicitly state when not to use it, mention prerequisites, or reference alternatives among sibling tools. Guidance is implicit rather than direct.

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