cdek_update_order

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

With no annotations provided, the description carries full burden. It discloses the key constraint (status condition and no cargo movement) and that it is a PATCH operation. It does not mention side effects, authentication requirements, or response details, so the transparency is moderate.

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 concise with only a few lines, front-loading the purpose and the key condition. It mixes English and Russian but is reasonably structured. Minor improvement could be separating the condition more clearly.

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 tool complexity (4 params, 0 required, no annotations) and presence of an output schema, the description covers the essential update condition and parameter roles. However, it lacks details about error handling, return values (though output schema exists), and usage compared to sibling order tools. It is adequate but not thorough.

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 explains each parameter: uuid (CDEK system ID), cdek_number (alternative tracking number), comment (new comment), delivery_point (new pickup point code). It also clarifies that uuid and cdek_number are mutually exclusive but at least one required. This adds meaning beyond the schema's titles and defaults.

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 clearly states the tool updates an existing order ("Изменение заказа") and specifies the HTTP method (PATCH /v2/orders). It distinguishes itself from siblings like cdek_create_order, cdek_get_order, and cdek_delete_order.

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 specifies the condition: update is possible only when the order status is 'Created' and no cargo movement at the CDEK warehouse. It states the requirement that at least one of uuid or cdek_number must be provided. However, it does not explicitly list when to use this tool versus alternatives.

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