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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value by naming the data returned, but it says nothing about default behavior when from/to are omitted, interval defaults, or the fact that idempotentHint=false is declared. Useful but not rich.

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, well-formed sentence that front-loads the resource and immediately lists the returned fields. No wasted words, though it is slightly dense with parenthetical expansion of TVL.

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 usefully enumerates the return fields. However, for a tool with all-optional parameters and no required inputs, it omits any explanation of default ranges, interval/count defaults, or result ordering, which an agent would need to call it 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 description coverage is 100%, with each of the four parameters documented in the schema itself (timestamps, count, interval). The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

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 states a specific verb and resource ('Returns historical Total Value Locked (TVL) data') and enumerates the components returned (pooled value, bonded value, total locked value), so an agent knows exactly what this fetches. It does not, however, differentiate itself from the many sibling history tools such as get_liquidity_history or get_rune_history, leaving the agent to infer which history endpoint is appropriate.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives, despite a crowded set of similarly named *_history siblings. The agent gets no signal about which history tool to pick or what conditions favor this one.

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