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

With no annotations, the description carries the full burden and delivers: it warns that already collected data is not recalculated, advises rerunning the check, and clarifies that underlying WB/Ozon differences are irrelevant. This is strong side-effect disclosure for a setter.

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, each earning its place: action, platform nuance, and side-effect warning. No filler and the main purpose is front-loaded.

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 one-parameter setter with an output schema, the description covers the essential behavior, parameter semantics, and post-condition. It could mention how to read the current region, but that is a routing nicety rather than a correctness gap.

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 0%, but the description compensates: 'достаточно назвать город' tells the agent the parameter is simply a city name and platform-specific codes are not required. This adds real meaning beyond the bare string type.

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 opens with 'Меняет город, из которого смотрятся цены на Wildberries и Ozon' — a specific verb, resource, and purpose. It clearly distinguishes this setter from the sibling getter parsee_get_region.

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 gives clear context: use this tool to change the city used for price lookups, and rerun the check after changing. It does not explicitly mention alternatives like parsee_get_region, but the usage scenario is unambiguous.

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