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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and openness profile is covered. The description adds meaningful context by naming the return payload (OHLCV candles) and flagging that data is live rather than historical, but it says nothing about market-hours behavior, staleness/refresh, or invalid-ticker handling.

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 with the core purpose front-loaded and zero filler. Every clause (OHLCV, ticker, range, live data) carries information.

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 low-complexity, two-parameter read tool with no output schema, the description is nearly sufficient: it names the metric set (OHLCV) and scope (ticker, range). It stops short of describing candle granularity or interval, which the agent cannot infer from the schema.

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 50%: ticker is documented in the schema, and range is self-documenting via its enum. The phrase 'over a range' loosely ties the parameter to intent but adds no format, semantics, or default detail beyond what the schema already provides, 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 (Get) and resource (OHLCV price-chart candles) scoped to a ticker and range, which cleanly separates it from siblings like get_company_profile or get_daily_trading_plan. An agent can identify the tool's output shape without opening the 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?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many sibling tools. The parenthetical '(Live market data.)' hints at freshness but does not tell the agent when this is the right tool versus, say, get_daily_trading_plan or get_market_overview.

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