Delivery: upload areas [sandbox]

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

Annotations indicate this is a write operation (readOnlyHint=false) but not destructive. Description adds context about the area format and the address classifier, but does not detail behavioral traits like idempotency or what changes occur to existing areas.

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?

Three sentences efficiently convey purpose and key details with no wasted words. Front-loaded with the core action, then adds critical context.

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?

Adequate for a sandbox tool with basic parameters and no output schema. Lacks information about the response, error handling, and behavior on success, but sufficient for initial understanding.

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 each parameter. Description enhances by clarifying that the areas parameter is the request body and specifying the address classifier (Russian Post postal codes), adding value 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?

Description clearly states the tool uploads areas for a tariff using Russian Post postal codes. The verb 'uploads' and resource 'areas' are specific, and it distinguishes from siblings like 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?

Explicitly states 'For delivery-service partners only,' providing a key usage restriction. However, it does not give explicit guidance on when to use this tool versus alternatives like delivery_add_terminals_sandbox.

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