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

Annotations already cover read-only and open-world traits, and the description adds real operational context beyond them: it is a pay-per-call endpoint billed in x402 USDC on Base, and a missing payment returns a payment challenge rather than an error. That payment/auth behavior is exactly the kind of disclosure annotations cannot provide.

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 tightly packed sentences with zero filler: data scope first, payment behavior second. Everything is front-loaded and no sentence is redundant.

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 an output schema present, return values need no explanation, and the payment flow is disclosed. The only minor omission is what happens on filtering by an unknown chain, but for a simple one-param read tool this is effectively 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?

Schema coverage is 100% and the single optional chain parameter is fully documented in the schema with an example (Ethereum). The description's only added semantic is the top-15 default when chain is omitted, which the schema already hints at, so this sits at the baseline.

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 resource (DeFi TVL), the data source (DeFiLlama), the scope (by chain, top 15 + total), so an agent knows exactly what the tool returns. It is clearly distinct from siblings like yields, funding, or macro.

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 only implied: the optional chain param and the note that omission yields the top-15 ranking convey the default behavior, but there is no explicit when-to-use guidance or comparison to sibling tools such as yields for protocol-level data.

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