get_last_prices

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

Annotations declare readOnlyHint=true, confirming the safe read semantics implied by 'Получить' (Get). The description adds temporal context ('текущие' / current) and domain scope ('Т-Инвестициях'), but omits behavior details like cache duration, handling of invalid tickers, or rate limits that would help an agent predict outcomes.

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 sentence, no redundancy, immediately conveys the operation and scope. Efficient structure with the verb front-loaded.

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 simple read tool with single parameter and no output schema, the description adequately covers the domain (T-Investments) and operation. However, absence of return value description or error behavior leaves gaps since no output schema is provided to compensate.

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 'tickers' fully documented as an array of strings (1-100 items). The description mentions 'по тикерам' (by tickers), aligning with the schema but not adding syntax, format, or example details beyond the structured definition. With complete schema coverage, baseline 3 is appropriate.

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?

Specific verb+resource: 'Получить текущие рыночные цены' (Get current market prices). The temporal qualifier 'текущие' distinguishes from historical data siblings (get_candles), and domain 'Т-Инвестициях' scopes the data source. Does not explicitly name alternatives but implicitly differentiates via 'current'.

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 this versus get_order_book (which also contains price data), get_candles (historical), or get_asset_fundamentals. No mention of prerequisites (e.g., market hours) or limitations.

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