List inventory write-off documents for a specified period and organization ID to review or manage write-off records.
Список актов списания за период. Где взять ID: organizationId → organizations__get_organizations. Троттлинг MCP-сервера (не лимит iikoCloud): не чаще 10 запрос(ов) за 60 с — кэшируйте результат в диалоге.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a throttling constraint (max 10 requests per 60s) and caching recommendation, which are valuable behavioral details beyond annotations. It does not contradict annotations.
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?
Two short sentences: the first states purpose, the second covers ID sourcing and throttling. No filler, front-loaded with the core purpose. Efficient and to the point.
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 list operation with three required parameters, the description provides purpose, ID source, and throttling guidance. It does not mention pagination or response format, but annotations cover read-only safety and the schema documents parameters. Adequate for an agent to call 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?
The schema itself provides descriptions for from, to, and organizationId (format and type), so the baseline is 3. The description adds value by telling where to get organizationId (via organizations__get_organizations), which is useful. It does not explain the from/to format further, but the schema already does.
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 the tool lists write-off acts for a period, which is a specific verb and resource. It distinguishes from get_inventory_writeoff_document (singular) by implying a list, and from other list tools by the resource name. However, it does not explicitly differentiate from sibling list tools like list_inventory_production_documents, though the name does that.
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 provides guidance on where to obtain organizationId and mentions throttling/caching, but it does not explicitly state when to use this tool versus alternatives. It lacks exclusions or comparisons to other list tools or the singular getter, so an agent must infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.