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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral information not present in structured fields: this is a paid call costing $0.003 USDC via x402. That payment-gating detail is exactly the kind of non-obvious operational trait an agent needs before invoking. It omits rate limits, pagination, and caching behavior, keeping it out of the top band.

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?

Two sentences, front-loaded with what the tool returns before the cost caveat. Almost every clause earns its place by adding a metric, provider, or constraint. Slightly dense with provider name-dropping, but there is no filler or redundancy.

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?

With no output schema, the description carries the burden of describing returns, and it does well by naming the metrics (APY base/rewards, 30-day average, TVL). For a read-only open-world data tool with annotations already covering the safety profile, this is close to complete. The main gap is the undocumented limit parameter and lack of sorting/pagination semantics.

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 0%, so the description is the only source of parameter meaning. It partially compensates by implying a chain filter ('filterable by chain') and by listing valid asset values (ETH, SOL, BTC), which maps to the asset parameter. However, the limit parameter is never mentioned, and no formats, defaults, or allowed values are given despite all three params being optional and undocumented.

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 a specific resource (liquid staking and restaking yields) and enumerates the exact metrics returned (APY base/rewards, 30-day average, TVL) plus the providers covered (Lido, Rocket Pool, Jito, etc.). This is far more concrete than a tautology and lets an agent know exactly what data is served. It loses a point for not distinguishing itself from the sibling defi_yields, which appears to overlap.

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 only usage cue is 'filterable by chain', which describes a capability rather than when to select this tool. There is no guidance on when to use staking_rates versus defi_yields, defi_tvl, or other yield/TVL siblings, and no exclusions or prerequisites are stated. An agent must infer the scenario entirely from the resource name.

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