⚠️ Заказы: самовывоз (детали)

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

Annotations indicate readOnlyHint=false and openWorldHint=true, implying modification and external side effects. The description says 'Подготовка заказа' (preparation of order), which suggests it modifies the order. However, it does not detail what changes occur (e.g., order status updates, notifications) or any constraints. No contradiction with annotations.

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 very short (two sentences) and concise. It includes a warning emoji and a brief explanation of a key parameter. While not verbose, it could be more structured with clear sections. Still, it is efficient.

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 the complexity (7 parameters, no output schema), the description is insufficient. It does not explain the overall effect on the order, the return value, or how parameters like address and details are used. The tool's behavior is unclear beyond bookingPeriod.

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 parameter descriptions are already present. The description only adds context for bookingPeriod ('период бронирования (часов)'), which is redundant with the schema. Other parameters like dryRun and idempotencyKey have detailed descriptions in the schema already.

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 title and description clearly state that the tool is for preparing a click-and-collect (self-pickup) order. It specifies the bookingPeriod parameter. However, it does not fully elaborate on what 'set details' entails beyond the booking period, leaving some ambiguity compared to sibling tools like orders_apply_transition.

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 no guidance on when to use this tool versus other order-related siblings such as orders_accept_return_order or orders_apply_transition. There is no mention of prerequisites, context, or exclusions.

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