⚠️ Заказы: выбрать слот курьера

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

Annotations declare non-destructive (destructiveHint: false) and non-idempotent behavior. The description does not add behavioral details beyond the schema (which includes dryRun and idempotencyKey parameters). No contradictions 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?

Two concise sentences with no unnecessary words. The first sentence states the purpose, the second gives a critical prerequisite. Every word earns its place.

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 10 parameters (7 required), no output schema, and the presence of a sibling tool for interval retrieval, the description adequately addresses the tool's role and prerequisite. It could be improved by mentioning the effect on the order or expected response, but it is sufficient for the complexity.

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 covers 100% of parameters with descriptions; the tool description adds no additional semantic meaning beyond stating the prerequisite. Baseline score of 3 is appropriate.

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 selects a time slot for courier arrival (выбор временного промежутка для приезда курьера) and references the sibling tool for getting intervals. The verb 'выбрать' aligns with the tool's function, distinctly differentiating it from orders_get_courier_delivery_range.

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?

Explicitly instructs to first call orders_get_courier_delivery_range to get available intervals, which is the primary usage guidance. It does not mention when not to use the tool or provide exclusion criteria, but the prerequisite is clearly stated.

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