Delivery: upload areas [sandbox]

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds context: 'The address classifier is Russian Post postal codes (1 postal code = all addresses belonging to it).' However, it does not clarify whether the upload replaces or appends existing areas, or mention sandbox-specific behavior beyond the tag.

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 three sentences, each serving a clear function: purpose, classifier detail, and audience. No redundant information. Efficient and front-loaded.

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?

Despite high schema coverage, the description lacks key contextual details for a mutation tool. It does not explain whether the upload replaces or appends areas, what validation occurs, or sandbox environment implications. The tool's complexity (nested objects) is not addressed in the description.

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 detailed descriptions for all parameters. The main description adds minimal extra meaning: it explains that areas are an array and that zipCodes are Russian postal codes. This is useful but not significant beyond the schema.

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 clearly states the tool's action: 'Uploads the areas where courier delivery/pickup is available for the specified tariff.' It specifies the classifier (Russian Post postal codes) and audience (delivery-service partners only). This distinguishes it from siblings like delivery_add_terminals_sandbox or delivery_add_sorting_center.

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 explicit guidance on when to use this tool versus alternatives. It mentions it is for delivery-service partners only, but does not state prerequisites (e.g., tariff must exist) or when not to use it. No mention of alternatives or exclusions.

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