Create saved package

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

Annotations already declare mutation plus non-idempotent/openWorld, so the description adds real value on top: which packaging types require length_in/width_in/height_in, that flat-rate needs none, and that weight_oz 0 defers weight to each label. It does not say what happens on duplicate titles or whether the new package is returned.

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, front-loaded with the core action and followed by the constraints an agent actually trips over. The parenthetical field list is mildly redundant but nothing is wasted.

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 with no output schema, the description covers the highest-risk ambiguity (which dimensions each packaging type demands) and the weight_oz=0 escape hatch. Remaining gaps are secondary optional flags rather than call-blocking unknowns.

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 coverage is only 38% and several params (length_in, width_in, height_in, irregular, packaging, signature, insured_value_usd, hazardous_materials) carry no schema description. The text compensates well for the dimension and packaging params but leaves signature, insurance and hazardous-materials semantics entirely unexplained.

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 (creates a Saved Package) plus the payload it stores (type, size, weight, extra services) and where it appears in Settings. That distinguishes it from create_shipment and from the update/delete/list saved-package siblings, though no sibling is named 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?

The conditional dimension rules imply when a given packaging choice is valid, and 'for reuse on labels' hints at the create-a-template-vs-one-off scenario. However it never says when to call this instead of update_saved_package or instead of passing dimensions directly to create_shipment, and no prerequisites are stated.

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