Orders: create labels (up to 1000)

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

Discloses key behavioral traits beyond annotations: async (returns taskID), rate limit of 1 request per minute, and that it generates labels for a batch. Annotations are not contradicted and the description adds useful operational context.

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 sentences: first states purpose and key differentiators, second describes usage flow. Every word adds value, no 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?

Despite no output schema, the description explains what the tool returns (taskID), how to proceed (wait, download via sibling), and constraints (pickup-point only, rate limit). This is complete for an async label generation tool.

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 100% with good descriptions for each parameter. The tool description adds context about async behavior and the download step, which complements the parameter descriptions but does not add significant parameter-level details. Baseline 3, increased for additional workflow context.

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 creates a task to generate PDF labels for a batch of orders (up to 1000), specifies it's for pickup-point orders, and distinguishes it from the sibling orders_generate_labels by highlighting higher order limit and stricter rate limit.

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 contrasts with sibling (orders_generate_labels) by order limit and rate limit, states availability only for pickup-point orders, and outlines the usage flow: returns taskID, wait, then download via orders_download_label.

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