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

Annotations already declare that this is a non-read-only, non-idempotent, destructive, open-world operation. The description adds only the generic purpose and does not mention duplicate-title behavior, side effects, permissions, or what "destructive" means for a saved package.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately concise, though its brevity contributes to gaps handled in other dimensions.

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 13-parameter mutation tool with low schema description coverage and no output schema, the description is too thin. It does not provide enough parameter or behavioral context for an agent to invoke it confidently.

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 low (38%), so the description needs to compensate. It only broadly groups parameters into "type, size, weight, extra services" and does not explain required fields like title and packaging, the default/irregular flags, or most optional services.

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 specific verb and resource ("Saves a package") and enumerates the main dimensions it captures, so the basic purpose is clear. It does not explicitly distinguish itself from siblings such as update_saved_package or list_saved_packages, leaving some ambiguity.

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?

It only implies that the tool is for saving reusable package settings ("for reuse on labels"). It gives no guidance on when to use this versus update_saved_package, list_saved_packages, or creating a shipment directly.

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