Orders: courier time slots

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

Description adds value beyond annotations by disclosing that the tool is read-only (redundant but consistent) and by revealing the response structure (dateOptions with intervals and intervalType). Annotations already cover readOnlyHint and idempotentHint, but the description provides practical behavioral context without contradictions.

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 compact (three sentences) with purpose front-loaded. Every sentence adds value: purpose, usage order, and warning against confusion. No fluff or redundancy.

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 no output schema, the description provides a glimpse of the return structure (dateOptions with intervals and intervalType). Combined with clear purpose and annotations, it is mostly complete, though a bit more detail on the exact response format would improve completeness.

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?

Both parameters have complete schema descriptions (100% coverage), so the description does not add extra meaning. It stays at baseline 3 as it does not enhance understanding beyond what the schema already provides.

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?

Description clearly identifies the action ('Returns'), resource ('available time slots'), and context ('for seller-courier delivery'). It explicitly distinguishes from the sibling 'orders_set_courier_delivery_range' by stating this one only reads and does not book.

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?

Description provides explicit guidance to call this tool BEFORE the set version and explains how to use the response (choose a slot from dateOptions). It contrasts with the set sibling, though it does not elaborate on when not to use it or alternative tools.

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