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

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

Annotations indicate non-read-only, non-destructive, non-idempotent, and open world. The description only adds '[SANDBOX]', which is already evident from the tool name. No additional behavioral context (e.g., side effects, rate limits, authorization) is provided beyond what annotations already convey.

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 extremely short (one line). While concise, it lacks substance and does not earn its place by providing useful information beyond the tool name. A slightly longer description with key details would be more helpful.

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?

Given the complexity (8 parameters, no output schema), the description fails to explain what the tool returns, any side effects, or how the parameters interact. It also lacks context about the sandbox environment's constraints. The description is insufficient for an AI agent to fully understand the tool's behavior.

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%, so the schema already documents all parameters. The description does not add any extra parameter information; it relies entirely on the schema. Baseline of 3 is appropriate as the description adds no additional semantic value.

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 'Загрузка нового тарифа (v2)' in the context of 'SANDBOX' clearly states the action (upload) and resource (tariff). The purpose is clear, but it does not distinguish from sibling tools like delivery_add_areas_sandbox or delivery_add_terminals_sandbox, which have different purposes.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, limitations (e.g., sandbox-only usage), or cases where sibling tools like delivery_add_areas_sandbox should be used instead.

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