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

Annotations already declare the read-only, idempotent, non-destructive, open-world profile, and the description adds substantial context on top: the x402 payment model ($0.01/call on Base), the prepaid x-credit-token header for unlimited calls, one free call/day, and no API key requirement. It also flags a real behavioral subtlety — tvlUsd is global TVL while chain filters presence, not per-chain TVL — which the agent could otherwise misread.

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 purpose, then filters, then the TVL caveat and pricing — a sensible ordering with every element doing work. It loses a little to marketing filler ('The DeFi-rankings commodity, served cheap', 'Not financial advice') that does not help an agent call the tool correctly.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. What remains — filtering behavior, the global-TVL caveat, and the payment/auth path — is fully covered, leaving nothing an agent needs to invoke this tool correctly.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: category examples (Lending, Dexes), the limit ceiling of 50, and critically the explanation that chain filters protocol presence rather than per-chain TVL. That last point corrects a likely misinterpretation, which is exactly the value a description should add over structured fields.

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?

Specific verb+resource: 'Top DeFi protocols by TVL', immediately scoped as filterable by chain and category, and explicitly excludes CEX/Chain/Bridge so the agent knows this is genuine DeFi rankings rather than a generic market list. It is clearly distinguishable from siblings like yield_scout or token_pools without opening any schema.

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?

Gives concrete usage context: pass chain= (e.g. base) to filter to protocols active on it, category= (e.g. Lending, Dexes) to narrow, limit= up to 50. It does not name a sibling alternative or state when NOT to use this tool, so it stops short of the explicit routing an agent gets from the best definitions, but the filter semantics are unambiguous.

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