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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description's only added behavioral fact is that window defaults to ALL, which is genuinely useful, but it says nothing about the granularity of the returned history, how 'latest frame' relates to the series, or any size/latency limits on a long ALL window.

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 short sentences front-loading the core action and the window semantics; nothing is padded. The 'Examples:' line is largely redundant with the description itself and is the one piece that does not earn its place.

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 3-parameter tool with 0% schema description coverage, the description is too thin: chainId is entirely unexplained and the meaning of address is left to inference. The output schema means return values need not be described, but the missing chainId/default-address semantics is a real gap an agent would hit on first call.

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 carry parameter meaning, and it only partially does: it explains the window values and the ALL default (which the enum alone cannot convey, since enums do not express defaults). It says nothing about what 'address' identifies (market address vs. token contract, ambiguous given the large sibling set) or what chainId is for and whether it has a default.

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 price history + latest for a market') and adds the scope detail that a time window applies. It is reasonably distinguishable from siblings like get_market_state or get_market_depth, though the description never explicitly contrasts itself with them; the tools most likely to be confused with it (get_perp_index_bars, get_market_trades) are not mentioned.

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 only guidance is a single trivial example ('Read the 1D price history for a market'), which restates the obvious rather than explaining when to pick this over get_market_state, get_market_depth, get_perp_index_bars, or get_market_trades. No when-not conditions, no prerequisites, and no note on when a caller wants a candle series versus a current snapshot.

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