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

The description discloses substantial behavior beyond the all-false annotations: output is plain text, no prices are included, Pro receives a .txt download link valid for one hour, and an existing out_path is refused unless overwrite is requested. It also signals the failure mode for naming conflicts. No contradiction with annotations exists.

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 capture the main result and the Pro file behavior with no filler. Every clause adds useful information: content details, tier access, absence of prices, download link expiry, naming, and overwrite policy.

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 no output schema and uninformative annotations, the description must carry the burden of explaining return values and edge behavior; it does so by specifying the slip contents, the no-prices guarantee, the download link expiry, and the overwrite refusal. The Pro plan prerequisite is implied and supported by the schema. The description is complete for a simple text-producing 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?

The input schema covers all four parameters with meaningful descriptions, including Pro-only status and overwrite behavior, so the description does not need to duplicate parameter details. The tool description adds global context such as the one-hour link and no-prices rule, but not per-parameter semantics. Baseline 3 is appropriate given full schema coverage.

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 identifies the deliverable: a packing slip as plain text with cartons, contents, weights, a signature line, and no prices. Combined with the title, it is evident this tool produces a slip rather than managing lists. It does not explicitly differentiate from sibling tools like packing_list_show, but the content specification makes the resource distinct.

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 guidance is given on when to choose packing_slip over sibling tools such as packing_list_show, packing_list_status, or packing_expect. The tier note (every tier vs Pro) is the only usage context, and even that focuses on output format rather than decision logic.

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