create_draft_shipment

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

No annotations are provided, so the description carries the full burden. It discloses that the tool creates a draft without immediate payment and saves data, but does not mention side effects, return values, or authentication needs. For a creation tool, more detail on the draft state and its lifecycle would improve transparency.

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, front-loaded with purpose and step context. No wasted words; every sentence contributes to understanding the tool's role and usage.

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 description covers the purpose and sequence well, but with no output schema and no annotations, it lacks details about return values (e.g., shipment ID) and potential side effects. For a 6-parameter nested tool, the description is adequate but not fully complete.

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 schema already describes all parameters. The description adds only a general statement about saving address and package info, and does not elaborate on optional parameters like cheapest_rate_id or label_print_type. Thus it adds marginal value beyond the schema.

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 states the verb '创建' (create) and resource '运单草稿' (shipment draft), and explicitly places it as step 2 between get_shipping_rates and pay_shipment, distinguishing it from sibling tools.

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 explicitly states when to call (after get_shipping_rates, before pay_shipment) and what it does (saves address and package info). It does not mention when not to use, but the sequential context provides clear guidance.

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