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

Annotations already flag destructiveHint=true and openWorldHint=true, so safety framing is partly covered. The description adds that a brand-new label is minted rather than reusing the old one, but it never says what happens to the original label (voided? still billable?), nor whether the operation incurs a new carrier charge — material gaps for a destructive, open-world mutation.

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 short sentences, zero redundancy, with the core action front-loaded and the important edge case (already-complete orders) placed second.

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 destructive, open-world mutation with no output schema, the description should say whether the returned artifact is a new label ID and what the caller does with it. It covers the conceptual model well but leaves the outcome of the call and the fate of the prior label unspecified.

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 100%, so the baseline is 3; the description adds meaning by explaining that the order, carrier contract and product are all inherited from labelId, reinforcing what the schema's "copy shipment settings from" implies. It says nothing extra about intentId, keeping it from a 5.

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 and resource ("Create a NEW shipping label") plus the scope that distinguishes it: it clones the order and carrier contract/product from an existing label. This makes it recognizably different from CreateLabelForOrder, but no sibling is named explicitly, so it stops short of a 5.

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?

"Works even when the order is already complete" implies when this tool is applicable versus a normal label creation, but the agent must infer the alternative (CreateLabelForOrder) and there is no explicit when-not guidance or stated prerequisite that the labelId must be a valid previous label.

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