Создать оприходование товаров

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

Goes well beyond the annotations by disclosing that the created document is unposted, that posting produces entries Дт 41 Кт 91.01, and that confirm=false performs a preview with no write. This is exactly the behavioral context an agent needs for a mutating tool with destructiveHint=false.

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?

Four telegraphic clauses, front-loaded with the resource and its unposted state, then the follow-up tool, the optional basis document, and the preview rule. No filler.

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?

With a full output schema, 100% parameter coverage, and detailed annotations, the description supplies the remaining essentials: unposted status, accounting effect, follow-up tool, and the preview/confirm protocol.

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% and the schema already documents confirm, operationId, inventoryRef and warehouse in detail, so the description only duplicates the dry-run/confirm idea and the inventory-basis hint. It adds little semantic value beyond the structured fields.

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?

Names a specific verb and resource ('Создаёт документ «Оприходование товаров» (излишки)') and immediately distinguishes the result state as unposted, separating it from sibling create_writeoff/create_inventory and from post_document.

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?

Explicitly routes the posting step to post_document and states that an inventory document may serve as the basis, plus the dry-run/confirm workflow. It stops short of contrasting surplus receipt against writeoff or plain inventory creation, which an agent must infer from sibling names.

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