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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond annotations: the exact per-line result categories ('есть', 'артикул есть у марки X...', etc.) and instructions to show price, check date, and links to the user.

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 front-loaded with purpose, then usage, parameter handling, and output expectations. It is fairly dense but every section adds operational value; some details repeat schema descriptions, preventing a 5.

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?

There is no output schema, so the description appropriately explains both the per-line result states and how the agent should present results to the user. Combined with strong annotations and full schema coverage, the definition gives enough context to call and interpret the tool correctly.

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%, so the schema already documents article, brand, name, and qty. The description nevertheless reinforces required vs optional fields and adds practical semantic guidance for brand transliteration ('Mercedes-Benz, BMW, Hyundai/Kia — не «Мерседес»') and the 50-line batch limit.

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 states a specific verb and resource: 'Сверить список деталей с витриной неликвида'. It makes clear this is a batch list-checking tool, which is distinct from the sibling tools get_part and search_parts that imply single-part lookup/search.

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?

It explicitly says when to call it: 'Звать, когда у пользователя список запчастей, заказ-наряд, счёт или рекомендации по ремонту'. It does not name when-not to use it or explicitly contrast it with search_parts/get_part, so it falls short of the top score for alternatives.

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