set_purchase_method

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

No annotations are provided, so the description carries the full burden. It discloses an important behavioral consequence—'Цены и наличие зависят от него'—but does not explicitly state that the tool mutates the current cart/order state, whether authentication is required, or what happens if an ID is missing/invalid. Some behavior is described, but significant gaps remain.

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 compact and front-loaded: a one-line purpose sentence followed by a bullet-style breakdown of the three options. Every sentence carries information, and the formatting makes the parameter-to-method mapping easy to scan.

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 moderately complex setter with an output schema, the description covers the method choices, their required parameters, and where those parameters come from. It leaves out explicit error/authorization behavior, but the agent has enough to select the tool and construct a valid call.

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 description coverage is 0%, so the description must compensate. It maps each enum value to the relevant optional ID parameter and its source (e.g., 'pickup_store — самовывоз из гипермаркета (нужен store_id из list_stores)'). This adds real meaning beyond the raw schema, though it could be more explicit about leaving unrelated IDs null.

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 states a specific action ('Выбрать способ получения и точку') and immediately names the three allowed methods. The enum values are explained in plain language, making it clear the tool sets the purchase fulfillment method, distinct from list_stores/list_pickup_points which are data sources.

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?

For each method the description states which parameter is required and where to obtain it: store_id from list_stores, address_id from profile, pvz_id from list_pickup_points. This gives an agent explicit when-to-call and how-to-prepare instructions, with the alternatives named.

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