get_candles

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

Annotations declare readOnlyHint=true. Description adds value by specifying OHLCV data format and T-Investments data source. However, lacks details on pagination, volume limits, or timezone handling that would help predict response size.

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?

Single dense sentence with zero waste. Front-loaded verb, parenthetical clarification of OHLCV acronym, and source attribution maximize information density.

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?

Adequate for a read-only data retrieval tool with 100% parameter coverage. Mentions OHLCV to hint at return structure where no output schema exists, but lacks details on array format, timezone normalization, or trading schedule considerations.

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% with excellent Russian descriptions for all 4 parameters including ISO 8601 format examples. Description mentions 'по тикеру' (by ticker) but doesn't add syntax guidance beyond what schema provides; baseline 3 appropriate for complete schema coverage.

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?

Clear verb 'Получить' (Get) with specific resource 'исторические свечи (OHLCV)' and source 'Т-Инвестиций'. Implicitly distinguishes from get_last_prices by specifying 'historical' candles, though explicit sibling comparison is absent.

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?

No guidance on when to use versus alternatives like get_last_prices (real-time vs historical), no mention of maximum date ranges, rate limits, or prerequisites for using different intervals.

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