⚠️ Orders: select courier slot

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

Annotations already indicate a write operation (readOnlyHint=false) and non-idempotence (idempotentHint=false). The description adds behavioral context: that it can be called again to change the time (allowed before pickup), and that the response contains a success flag. This goes beyond annotations but lacks details on error states or side effects.

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 extremely concise (3 sentences) and front-loaded with the purpose. Each sentence adds distinct value: purpose and type, usage guidance with prerequisite, and behavioral ability to change. No redundant or superfluous 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?

For a tool with 10 parameters and no output schema, the description covers the primary use case, key parameters, and return flag. However, it lacks details on error conditions (e.g., what if courier already picked up?), restrictions, and full output format. Still adequate for basic usage.

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?

Although schema coverage is 100% with good descriptions, the description adds critical semantic guidance: that startDate, endDate, and intervalType should be taken from the get method response. It also explains the dryRun and idempotencyKey parameters in context. This significantly aids correct use.

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's purpose: 'Selects (books) a specific time slot for a courier to pick up the item'. It explicitly distinguishes from the sibling tool orders_get_courier_delivery_range, which is a read-only method. The verb is specific and the resource is well-defined.

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?

Provides explicit usage guidance: 'call it first and take the interval and intervalType from the response', referencing the sibling tool. Also states that the tool can be called again to change the time while the courier has not yet picked up, giving clear when-to-use and when-to-reuse instructions.

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