cdek_reverse_availability

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

With no annotations, the description carries the burden. It discloses the success response (empty body with 200) but omits behavior on failure (e.g., error code) and any side effects. This is minimal but acceptable for a simple check endpoint.

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 brief, starting with purpose, then behavior, then parameter list. No redundant sentences, though the parameter list could be integrated into the schema. Front-loads the core function effectively.

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 has an output schema (so return values are covered elsewhere) and parameters have context from the description, it is fairly complete. Could mention that this is a prerequisite for reverse orders, but not critical.

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 by explaining each parameter's role, including nuances for shipment and delivery points ('от склада' / 'до склада'). It adds value beyond the schema's type/defaults, though defaults could be noted.

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 checks reverse delivery availability (реверса) before creating a direct order, and refers to the specific endpoint POST /v2/reverse/availability. This verb+resource combination distinguishes it from sibling tools like cdek_create_order or cdek_calculate_tariff.

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 use before creating a direct order when reverse delivery is needed ('до создания прямого заказа'). However, it does not explicitly state when not to use it or mention alternatives, though no alternative reverse-check tool exists among siblings.

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