logistics_create_shipment

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

No annotations are provided, so the description must bear the burden of disclosing behavior. It indicates it creates a shipment (write operation) and generates documents, but does not detail side effects, authorization requirements, or whether the shipment is actually dispatched. The note to review before dispatching hints that label creation is separate from dispatch.

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 brief, with two substantive sentences and an important note. It is front-loaded with the primary action, though the 'Station 1' label could be clarified.

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 tool has an output schema, so return values need not be explained. However, the description omits prerequisites (e.g., does the order exist? are there constraints?), and the 'Station 1' reference may confuse without broader workflow context. Overall adequate for a tool with well-described schema.

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 input schema has 100% description coverage for all 4 parameters, so the description adds minimal extra meaning beyond stating it creates a shipment 'for an order' and 'for international shipments', which is already implied by 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 it creates a shipment and generates shipping label, packing list, and customs docs. The verb 'create' and specific outputs make the purpose clear, though it does not explicitly differentiate from sibling logistics 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 mentions 'Station 1' implying an order in a workflow, and includes an important note to review before dispatching, but lacks explicit guidance on when to use this tool vs. alternatives like logistics_customs_declare or logistics_consignment_manifest.

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