getMarketIndicatorCandles

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds behavioral details: max 200 candles, pagination mechanism, rate limit group, and error responses. No contradictions.

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?

Well-structured with line breaks and bullet points. Front-loaded with main purpose, then detailed constraints. Every sentence adds value. No wasted words.

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?

Covers key aspects: purpose, supported symbols, intervals, pagination, error handling, rate limits. However, does not describe the response format or structure beyond 'OHLCV', which could be improved for completeness.

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?

Despite 100% schema description coverage, the description adds valuable context not in the schema (e.g., URL encoding for '+' in 'before' parameter, clarification of interval restrictions per symbol type). Adds meaning 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?

The description clearly states it queries market indicator candle chart data (OHLCV) with a max of 200 candles. It distinguishes from the sibling 'getCandles' tool by explicitly stating to use that for individual stocks.

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?

Provides explicit when-to-use guidance: which tool to use for individual stocks, which intervals are supported per symbol type, and mentions rate limit group. Also covers error responses for unsupported symbols and invalid requests.

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