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

With no annotations, the description carries the full behavioral burden and does well: it discloses the data source ('HyperLiquid candles, real, not fabricated'), the default window (24h), and the ticker universes covered (crypto and equities/RWA). It omits rate limits, error behavior, and pagination, but for a read-only stats tool this is solid disclosure.

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 purpose and the drawdown/bounce/open semantics are front-loaded in the first sentence, with triggers and coverage following. It is dense with parentheticals and ticker examples, but every sentence serves a purpose.

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 read-only tool with no output schema, the description compensates by enumerating the returned fields and their relative-move definitions, plus data provenance and window defaults. Nothing essential is missing, though failure modes and data freshness limits are unstated.

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 three parameters are already documented in the schema, making 3 the baseline. The description adds only marginal value by restating the 24h default and that 'hours' changes the window, plus example tickers, but no format or edge-case detail beyond the schema.

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 intraday/window OHLC stats for a ticker') and enumerates the exact fields returned (current price, high, low, open, and high/low/open-relative moves). An agent can distinguish it from the sibling get_price, though the description never names that sibling explicitly.

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?

Gives explicit triggering situations with quoted example queries ('how far off the high/low', 'today's high and low', 'change since open'), which is strong when-to-use guidance. It stops short of stating when NOT to use it or naming an alternative sibling (e.g. get_price) for plain price lookups.

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