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

The read-only framing is consistent with readOnlyHint=true, and the description usefully enumerates the returned data series, which matters since there is no output schema. It does not explain the implications of idempotentHint=false (results shift as new intervals accrue), nor pagination or interval defaults, so it adds only partial behavioral context.

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 with no filler, and the purpose plus the returned metrics lead the reader immediately. It could be slightly tighter, but nothing 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?

Since no output schema exists, listing the returned data fields is genuinely useful and partly compensates. Still missing for a time-series tool: how from/to/count/interval interact, what happens when they are omitted, and how this differs from the sibling history tools.

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%, so all five parameters (asset, from, to, count, interval) are already documented in the schema, making the baseline 3. The description adds no syntax, default, or interaction detail beyond restating the returned data 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?

States a specific verb and resource (historical depth data for a pool) and enumerates the metrics returned: asset depth, RUNE depth, asset price, liquidity units. However, it does not differentiate itself from closely named siblings like get_liquidity_history or get_rune_history, which an agent could easily confuse it with.

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?

No when-to-use guidance, no exclusions, and no mention of the alternative history tools (get_liquidity_history, get_tvl_history, get_earnings_history) that overlap in scope. The agent must infer selection purely from the tool name.

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