Delivery: upload areas [sandbox]

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

Annotations indicate a non-destructive, non-idempotent write operation. The description adds that it uploads areas but does not disclose whether it replaces or appends existing areas, or any other behavioral traits beyond what annotations provide.

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 concise with four sentences, front-loading the main purpose. Every sentence adds information, though it could be slightly more structured.

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?

No output schema is provided; the description does not explain return values or the dryRun/idempotencyKey parameters (though schema covers them). For a complex upload tool, it lacks information on whether the operation replaces or adds to existing areas.

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 explains parameters. The description adds context about postal codes being the classifier, which aids understanding of the zipCodes parameter, but overall adds limited value beyond 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 uploads areas for a specified tariff, specifies the address classifier (Russian Post postal codes), and indicates it is for delivery-service partners. It distinguishes itself from sibling tools like delivery_add_sorting_center or delivery_add_terminals_sandbox.

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 mentions 'For delivery-service partners only' but does not provide explicit guidance on when to use this tool versus alternatives, or mention prerequisites or when not to use it.

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