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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the safety profile is carried for the description. The line 'nothing is bought' usefully clarifies no money moves despite the destructive hint, but it doesn't say what happens to the source orders or how partial failures are handled — the key risk for a destructive, non-idempotent tool.

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?

One compact sentence with the core action front-loaded and the 'nothing is bought' qualifier placed where it lands hardest. Zero wasted 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?

With five parameters, no output schema and a destructive annotation, the description should say what the agent gets back and what happens to the consumed orders. It covers the action and the no-purchase guarantee but leaves the outcome and side effects to inference.

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 all five parameters including the companion-tool pointers (list_import_orders, list_saved_packages) are already documented. The description only echoes the 'one saved package' constraint and adds no format or edge-case detail beyond the schema.

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?

States a specific verb and resource: turns orders into a batch of shipments. It also pins down the 'one saved package' scope, which implicitly separates it from create_batch, though it never names that sibling explicitly.

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?

'nothing is bought' is a useful exclusion that steers agents away from buy_label territory, and the package/order framing implies the pre-label workflow. But it never names alternatives (create_batch, create_shipment) or states prerequisites like having synced orders first.

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