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

With no annotations, the description must carry the behavioral burden. It discloses the metric distinction (fees vs revenue), the time windows, and the chain scope, but says nothing about sorting direction, pagination behavior, rate limits, or whether time windows are merged into one response. The output schema covers return shape, lowering the bar somewhat.

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 tight sentences with the core scope front-loaded and the use case following. No filler, no repetition of schema or title.

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 three-parameter data query with an output schema, the description covers the data domain but leaves one parameter (`limit`) completely undocumented and the metric enum values unstated. Adequate for a first read, but not complete enough to invoke confidently without inspecting the schema.

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 must explain all three params. It adds meaning for `metric` (fees vs revenue) and `chain` (all chains or one chain), but the `limit` parameter is never mentioned, and exact accepted metric values or chain identifier format are not given.

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 (crypto protocols) and measure (fees paid by users vs revenue kept) with time windows and chain scope, so an agent knows exactly what it returns. It does not explicitly name or differentiate from siblings like defi_protocols_tvl or chains_tvl, which keeps it from a 5.

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?

"Use for fundamental analysis and protocol valuation" gives a general use case, but there are no when-not conditions and no routing advice against the many adjacent DeFi/TVL/volume tools in the sibling list. Usage is implied rather than specified.

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