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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond them: prices hidden by default, three page sizes, long orders spilling to a second page, an accompanying pick list totalled by SKU plus CSVs, and that problems are listed per line. It does not describe how problems are surfaced (warnings vs. failure), which is the one gap.

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?

Front-loaded with the trigger phrase and tightly packed with facts, with the negative scope last. The keyword list in parentheses ('packing slip template', 'etsy packing slip 4x6', etc.) is somewhat padded but does real disambiguation work.

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 12-parameter, deeply nested tool with an output schema and rich annotations, the description covers input routes, output artifacts, defaults and exclusions. What remains thin is the relationship to the sibling generate_pick_list and the exact shape of per-line problem reporting.

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 description coverage is 100%, so the schema already documents all 12 parameters with examples. The description only lightly reinforces a few of them (show_prices, page sizes, supported export formats); it adds no format or constraint detail beyond what the schema states, so the baseline 3 applies.

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 ('generate packing slips'), enumerates the exact outputs (one-slip-per-order PDF, pick list PDF, CSVs) and lists the phrasings a user might use. The agent can tell this is packing-slip generation rather than the sibling generate_pick_list, even though the pick list PDF is a by-product here.

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?

'Use this when the user wants packing slips' plus synonyms gives an explicit trigger, and it explains the two input routes (convert pasted text/image into order objects first, or pass a Shopify/Etsy/WooCommerce/Amazon export). The closing sentence gives negative scope (no postage, labels, barcodes, or store changes). It never names the sibling generate_pick_list or when to prefer it, so it stops short of full when-not/alternatives guidance.

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