cdek_create_delivery

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

With no annotations, the description bears full burden. It explains the action (registering an agreement) and conditions for time/address fields but omits side effects, permissions, or error cases.

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 mixes Russian and English, and includes an API path and parameter list. It is somewhat verbose; could be more concise by removing redundant 'Args' lines after already listing them.

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?

Output schema exists, so return values need not be described. However, the description lacks usage scope (when to use) and does not cover non-parameter behaviors like side effects or prerequisites.

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 lists all 7 parameters with explanations and additional constraints (e.g., time_from/time_to mandatory for 'до двери', delivery_point for 'до склада', and the requirement for at least one of cdek_number/order_uuid).

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 registers a delivery agreement via POST /v2/delivery, fixing date/time and allowing address changes. It distinguishes from siblings like cdek_create_order and cdek_get_delivery.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., cdek_get_delivery, cdek_create_order). Only parameter constraints (at least one of cdek_number or order_uuid) are given.

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