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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds two useful non-annotation facts: no authentication is required and the response is timestamped price points. It still says nothing about series size, pagination, rate limits, sort order, or units/quote currency, which matter for a time-series read.

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?

Three short sentences, all earning their place, with the primary purpose front-loaded before the return shape and the auth note. No filler or redundancy.

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?

No output schema exists, so the description should carry more of the return-value burden; 'timestamped price points' is a start but omits ordering, point count limits, and units. Against a dense sibling set the lack of routing guidance leaves a real gap.

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 the baseline is 3. The description only reinforces that multiple tokens are accepted; it adds no format or interaction detail (e.g. resolution vs window interplay) beyond the schema's own text.

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?

Clear verb+resource ('Get historical price data for one or more tokens') and it names the return shape ('timestamped price points'). However, it never distinguishes itself from near-neighbours in the sibling set such as get_price_range, get_price_at_time, get_candles, or get_perp_market_history, all of which sound like the same job.

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 statement of when to use this versus alternatives, even though the sibling list contains at least four plausible substitutes (get_price_range, get_price_at_time, get_candles, get_price_indicators). The only usage constraint present (symbols vs asset_ids mutual exclusion) lives in the schema, not the description.

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