Автозагрузка: Ad ID по Avito ID

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds 'из файла' (from a file), indicating the source of Ad IDs, but does not elaborate on behavior like response format or limitations.

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?

The description is two sentences: first states the purpose, second describes the parameter. No unnecessary words, and it is front-loaded with the key action.

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 lookup tool with one parameter and rich annotations, the description provides sufficient context. The phrase 'из файла' hints at the autoload context. However, it could clarify whether 'из файла' refers to a file upload or internal file, but overall it is complete enough.

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 100%, and the description repeats the parameter explanation ('query — CSV-список Avito ID'). The schema already describes the parameter similarly, so the description adds minimal extra meaning.

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 'Получить Ad ID (из файла) по Avito ID', indicating the tool retrieves Ad IDs from Avito IDs. The name and title reinforce this. It distinguishes from the sibling tool 'autoload_get_avito_ids_by_ad_ids' which does the reverse mapping.

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?

The description explains the parameter format (CSV list) but does not explicitly state when to use this tool versus alternatives. The sibling tool is implied by name, but no direct guidance is provided. Usage context is inferred rather than explicit.

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