Top DeFi protocols by TVL

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

Annotations already cover the read-only and open-world profile, but the description adds genuinely useful provenance beyond them: the DefiLlama source and the nightly snapshot freshness, which tells an agent the data may be up to a day stale. It still omits pagination, default ordering beyond TVL, and response shape, so it stops short of full behavioral disclosure.

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?

A single front-loaded sentence naming the resource and ranking metric first, with the filter modifiers and data source trailing as parentheticals. No sentence is wasted.

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-parameter-required read tool with no output schema, the definition is workable but thin: it never says how many protocols come back by default, what fields each entry contains, or how chain/category values must be spelled. An agent can call it, but may need trial and error to get useful output.

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 0%, so the description must carry the load. It partially compensates by giving concrete category examples (Lending, Dexs, Liquid Staking) that the schema lacks, but 'limit' is never explained (default, max 100) and the expected format for 'chain' (slug vs. display name) is left ambiguous.

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 ('top DeFi protocols by TVL in USD'), its ranking criterion, and its data source. The word 'protocols' (versus the sibling 'chains_tvl') implicitly scopes it to a different entity class, so an agent can distinguish it from the chain-level TVL tool without opening either 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?

The description says the filters are optional but never states when to reach for this tool versus chains_tvl, nor what happens if filters are omitted. There is no when/when-not guidance or named alternative, so selection is left entirely to inference.

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