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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description only needs to add beyond that, which it does: the default interval, that output is in USD per coin, that ATR is oriented toward stop placement, and the disclaimer about not being a recommendation. It does not mention latency or data freshness of the candles, so it falls short of fully rich 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?

The indicator list and exclusions are front-loaded and every clause carries information, including the workflow pointer at the end. The 'Inputs: symbol (base coin), interval' fragment largely repeats the schema, which is the one piece of waste.

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 an output schema present and full annotation coverage, the description only needs to cover purpose, selection, and units, and it does all three for a simple two-parameter tool. Nothing required to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining what interval choice is appropriate for trend versus timing and by reiterating that symbol is a base coin with USD-denominated outputs. This goes past restating the enum and 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?

The description names the exact indicator set (RSI, MACD, Bollinger %B, ATR, EMA trend, volume rank), the resource (one coin), the data source (Hyperliquid candles), the interval set, and the funding-rate add-on. It also explicitly excludes two siblings (compare_venue_prices for live quotes, get_price_candles for raw prices), so the agent can separate it from adjacent tools without opening a schema.

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?

It states when to use the tool (as decision inputs), how to choose intervals ('1h or 4h for the trend and 15m for timing'), what it is not ('not a trading recommendation'), and where to go for the two overlapping use cases it does not serve. It even names the natural next step, size_position, giving a clear workflow slot.

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