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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so the safety profile is covered; the description instead contributes non-obvious semantics — that each point is a rolling 24h figure and that adjacent points overlap by nearly a full day, which prevents double-counting. It stops short of disclosing limits such as maximum point count, pagination, or behavior for unknown symbols.

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?

The core definition is front-loaded in the first sentence, with the interpretation caveat and doc pointer following in logical order. It is slightly long for a four-parameter read tool and the docs anchor is only marginally useful, but no sentence is filler.

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 carries the burden of explaining return values and does so — points are provider-reported rolling 24h USD figures at each timestamp. What remains unstated are edge cases such as empty series, maximum resolution span, or error behavior for invalid windows, which matters for an open-world read tool.

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 four parameters, including the symbol/asset_id mutual exclusivity and the resolution-vs-window constraint, are already documented. The description adds no per-parameter meaning beyond a pointer to an external docs section for window/resolution formatting, so the baseline 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?

States a specific verb and resource ('Get reported 24h volume history') plus the exact unit and configurability ('reported 24h volume in USD over a configurable lookback window, sampled at a configurable resolution'). Crucially it separates itself from the bucket-volume sibling: 'not the volume traded inside the bucket' tells an agent how this differs from get_candles.

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 definition draws a sharp semantic line between provider-reported rolling volume and per-bucket traded volume, which is effectively the criterion for choosing this tool over get_candles. However, it never names the alternative tool nor states when not to use this one; the routing is inferable rather than explicit.

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