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

The text clearly describes a state-changing mutation: moving statuses, recording shipping data, and freezing the list. This directly contradicts the annotation readOnlyHint=true. Per the rubric, a description that contradicts annotations scores 1 regardless of the useful freeze/irreversibility detail it adds.

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 short sentences with no filler. The first sentence front-loads the action and transition path, the second explains shipping side effects, and the third states the irreversible consequence. Each sentence earns its place.

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?

The core workflow and the irreversible shipped state are covered, and the schema fills parameter details. However, there is no output/return guidance, cancellation behavior is only named and not explained, and the annotation contradiction leaves the agent with conflicting signals about whether this tool mutates state.

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 schema already documents 6 of 7 parameters, so the baseline is 3. The description adds valuable cross-parameter meaning: carrier, tracking, and date are recorded specifically when moving to shipped, and status follows the draft->packed->shipped path. This helps the agent understand when those optional parameters matter.

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 ('Move') and resource ('packing list') and enumerates the exact status transitions: draft to packed to shipped, or cancel. It is clearly distinguishable from siblings like packing_list_create, packing_list_list, and packing_list_delete because it is the workflow-status mutation tool.

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 makes the tool's scope clear: use it when advancing or canceling a packing list's status. It does not explicitly name alternatives or state when not to use it, but the workflow context is specific enough for an agent to select it over the create/list/show/delete siblings.

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