Search Ozon delivery cities

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

Annotations already declare readOnly, idempotent, and openWorld, and the description adds the live dynamic behavior ('Live city lookup via Ozon maps API') and the exact return shape. This is meaningful context beyond the annotations, though no caveats about rate limits or API failures are mentioned.

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 compact sentences cover behavior, trigger, query format, return shape, and next step. Every sentence earns its place and the live-vs-static distinction is front-loaded, followed by clear usage instructions.

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?

Complete for a low-complexity, read-only search tool: it covers when to use, how to query, what the response contains, and what to do with the result. There is no output schema, but the return fields are listed, and the limit parameter is already documented in the schema.

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 practical query semantics—'Pass first letters or full name' with concrete examples ('Каз', 'Санкт', 'Екатеринбург')—which is not present in the schema and helps the agent form correct inputs.

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+resource: 'Live city lookup via Ozon maps API' and explicitly contrasts it with 'not a static list.' It also enumerates the returned fields (cities[]: label, city, region, lat, lng, uid), making the tool's function unmistakable and distinct from siblings.

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 provides trigger conditions: 'Use when user asks about delivery to a city or you need options to choose from.' It also defines the follow-up workflow with ozon_set_city(city). It does not contrast with potential sibling alternatives like ozon_get_location, so a small gap remains.

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