Set Ozon delivery city

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

Annotations only provide openWorldHint, so the description carries the behavioral burden. It discloses that this is a session-scoped mutation, that it takes ~20–40s, that it changes downstream delivery results, and it gives the response shape including requestedCity and location.

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 with no filler: prerequisite, parameter usage example, output shape, downstream impact, and latency are all packed efficiently. Key behavior is front-loaded and every sentence earns its place.

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 there is no output schema, the description compensates by stating the return fields. It covers the prerequisite call, parameter semantics, side effects, latency, and affected tools, making it sufficient for an agent to invoke and interpret the result correctly.

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%, so the baseline is 3. The description adds value by explaining how address is used to bias PVZ, providing concrete examples, and tying city/lat/lng to ozon_search_cities results, which complements the schema rather than repeating it.

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?

States a specific verb and resource: 'Change delivery city for the session' plus 'picks a pickup point via Ozon map'. Clearly distinguishes from siblings like ozon_search_cities and ozon_get_location by framing it as a mutating session-level operation with downstream effects.

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 instructs to call ozon_search_cities first to show valid options, which is strong usage guidance. Also explains how address biases PVZ selection and notes that the change affects ozon_product_details/ozon_product_offers, but stops short of naming alternatives or when-not-to-use cases.

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