Orders: create labels

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

Discloses behavioral traits beyond annotations: async task creation (returns taskID), limit of 100 orders, availability constraint (pickup-point only). Annotations already indicate non-read-only, non-destructive, so description adds valuable 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?

Three sentences, each carrying essential information. Front-loaded with purpose and limit, then availability and flow, then alternative. No redundant words.

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?

Covers all necessary context: input (orderIDs), constraints (pickup-point only, max 100), output (taskID), follow-up action (download label). No output schema but description compensates. Complete for a task-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%, so parameters are fully documented. The description mentions the orderIDs limit but doesn't add new semantics beyond schema. 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 creates a task to generate PDF labels for orders, specifying the resource and action. It distinguishes from sibling tools like orders_generate_labels_extended (higher limit, rate limit) and orders_download_label (download step).

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 when to use: only for pickup-point orders and for up to 100 orders. Directs to alternative for larger batches. Clarifies the async flow: returns taskID, 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.