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

With no annotations present, the description fully carries the behavioral burden: it discloses the output form, content fields, absence of prices, the Pro download-link behavior, the one-hour link expiry, and the refusal to overwrite an existing out_path unless explicitly requested. This gives the agent a realistic model of side effects and results.

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, front-loaded with the core output and contents, followed by the Pro-specific download behavior. No filler or 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?

For a 4-parameter tool with no output schema, the description explains what the caller gets back: plain text with a defined field set, or a one-hour .txt download link when out_path is supplied, plus overwrite semantics. Nothing essential for calling it correctly is missing.

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?

The input schema already documents all four parameters at 100% coverage, so the baseline applies. The description reinforces out_path and overwrite behavior but does not materially add syntax or meaning beyond the schema for divisor or packing_list.

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+resource: produce the packing slip as plain text, and goes on to define the exact contents (cartons, contents, weights, signature line) and a hard constraint (no prices). This separates it from packing-list management siblings such as packing_list_show or packing_list_create.

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?

The description implies when the tool is appropriate (when a plain-text packing slip is needed, on any tier, or a Pro-only .txt download) but never names an alternative or says when not to use it. The tier distinction is useful context, but routing to siblings is left to inference.

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