Доставка: загрузить СЦ [sandbox]

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

Annotations provide basic behavioral traits (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds no further behavioral context beyond the sandbox note. It does not disclose side effects, error conditions, or whether the operation is reversible.

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 a single concise sentence with no wasted words. It could benefit from additional context, but it is appropriately structured for a simple tool.

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?

The tool has three parameters and no output schema, yet the description does not explain the return value, success criteria, or error handling. It omits context about the sandbox environment's implications and does not leverage the available annotations to provide a complete picture.

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 descriptions for all parameters. The descriptions for 'dryRun' and 'idempotencyKey' are detailed and add value beyond the schema. However, the 'centers' parameter description is minimal ('Массив центров.') and references external documentation without clarifying the object structure. Overall, the description adds some but not significant additional 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 '[SANDBOX] Загрузка сортировочных центров' clearly indicates the action of uploading/adding sorting centers. The name and title align with this purpose. However, it does not differentiate from sibling tools like delivery_add_tags_to_sorting_center or delivery_add_areas_sandbox, leaving some ambiguity about the exact operation.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention prerequisites, limitations (e.g., sandbox only), or scenarios where other tools like delivery_get_sorting_center are more appropriate.

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