cdek_estimated_intervals

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 identifies the operation as a POST to retrieve intervals but does not disclose if it is read-only, idempotent, or if it modifies any state. The word 'получить' suggests a read, but behavioral traits like side effects or authorization needs are absent.

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: a single sentence stating purpose, followed by a clean parameter list. Every element adds value, though the parameter list could be slightly more compact. No extraneous information.

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 5 parameters and no annotations, the description covers the basics. However, it does not mention the output format or what the intervals contain (e.g., dates, times, availability). The presence of an output schema is noted but not leveraged in the description.

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%, so the description compensates with an Args section that adds meaning (e.g., 'Recipient city name', 'CDEK tariff code (default 136)', 'Date-time ISO format'). However, some parameters like date_time lack explicit format guidance, and shipment_point is only partially explained.

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 it retrieves delivery intervals before creating an order, with specific mention of 'до двери' (to door) and reference to the API endpoint. It distinguishes from siblings like cdek_create_order but does not explicitly differentiate from the sibling cdek_delivery_intervals, which may overlap.

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 implies usage 'before creating an order' but does not provide explicit guidance on when to use this tool versus alternatives like cdek_delivery_intervals or cdek_calculate_tariff. No when-not-to-use or exclusions are mentioned.

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