Produce the packing slip

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

With no annotations provided, the description carries the full burden and largely delivers: it discloses two refusal behaviors ('Refuses a URL', 'refuses to overwrite unless told'), a tier-gated side effect (file write only for Pro), and a content guarantee ('no prices anywhere'). It does not cover authorization, rate limits, or invalid-ID handling, but the non-obvious safety-relevant behavior is made explicit.

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 a distinct, non-redundant fact: the output content, the Pro-specific file write, and the refusal/guard rules. The tool's core purpose is front-loaded and there is no filler.

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 four-parameter tool with a fully self-describing schema, the description supplies output format, tier behavior, and override guard. It does not describe the exact error text when a write is refused, or whether a successful write also returns the slip, but overall the schema-plus-description covers what an agent needs to invoke correctly.

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% and every parameter — including overwrite's default-false refusal and out_path's Pro tiering — is already fully documented inside the schema. The description's 'refuses to overwrite' and 'Pro also writes it to out_path' largely restate the schema, adding little new parameter-level meaning, which keeps this at the baseline 3 despite it being a compact summary.

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 states a precise deliverable — a plain-text packing slip containing cartons, contents, weights, and a signature line — and explicitly excludes prices, which clearly scopes what the tool does. It distinguishes itself from list-oriented siblings like packing_list_show and carton_report by its content specification, though it never names a 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?

No explicit when-to-use guidance or named alternatives; the closest selection signal is the tier constraint ('Pro also writes it to out_path'). An agent can infer the scenario from the plain-text slip format, but the description does not actively say when to choose packing_slip over packing_list_show or carton_report, leaving that to context and the sibling names.

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