get_order_book

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

Annotations already declare readOnlyHint=true, confirming safe read-only access. Description adds valuable context by specifying the data source (T-Investments) and clarifying 'стакан заявок' means 'биржевой стакан' (exchange order book). However, lacks details on error handling for invalid tickers or rate limiting.

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 efficient sentence with zero waste. Front-loaded with the action verb, parenthetical clarification immediately defines the financial instrument type, and source attribution is clear.

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 simple read-only retrieval tool with two well-documented parameters. However, lacks description of the order book structure (bids/asks) that would be returned, which is relevant given no output schema exists.

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 clear descriptions for both ticker and depth parameters. Description mentions 'по тикеру' reinforcing the primary parameter, but adds no additional semantic information about the depth parameter or formatting constraints 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?

Uses specific verb 'Получить' (Get) and resource 'стакан заявок' (order book), with scope 'по тикеру' (by ticker) from T-Investments. Implicitly distinguishes from sibling get_orders (user orders vs exchange order book) and get_last_prices (depth vs prices), though lacks explicit sibling contrast.

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 no guidance on when to use this tool versus alternatives like get_last_prices or get_candles, nor does it mention prerequisites such as requiring a valid ticker from T-Investments markets.

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