Задать адрес доставки

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

With no annotations, the description carries full responsibility. It discloses the search priority for saved addresses, preservation of apartment/entrance/floor details, and fallback to map search. This goes beyond a generic 'set address' and gives agents valuable foresight into the tool's runtime behavior.

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 two sentences, directly front-loaded with the action. It uses capitalization for emphasis on key behaviors and contains no filler, making it highly concise and scannable.

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?

For a relatively simple tool with two parameters and no output schema, the description is sufficient. It covers the main workflow, including the saved-address shortcut and fallback, without unnecessary details. It doesn't address errors or authentication, but those are not critical for this type of operation.

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?

The schema already covers both parameters with descriptions (100% coverage), so the baseline is 3. The description adds value by elaborating the meaning of address as a label ('дом'/'работа') and how preferSaved controls the search-first behavior, plus the detail about not needing to re-click on the map when a saved address is used.

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 action ('Устанавливает адрес доставки') and identifies the resource (delivery address). It distinguishes itself from sibling read tools like get_address and list_saved_addresses by describing a write operation with specific behavior around saved addresses, making its purpose unambiguous.

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 clear context on when to use the tool: to set a delivery address, and explains the default behavior of first checking saved addresses and the fallback when none match. It doesn't explicitly list alternatives or exclusions, but the distinction from read-only siblings is implied.

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