Delivery: create parcel [sandbox]

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

The description adds value beyond annotations by confirming no real-world effect, sandbox context, and no consequences. Annotations already indicate non-destructive, but description reinforces the safe testing nature.

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 concise with four sentences, each serving a purpose: stating the function, return value, lifecycle links, and differentiation from production. Front-loaded and efficient.

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?

Despite lacking an output schema, the description adequately explains the output (parcelID) and the tool's role in the sandbox lifecycle. All parameters are documented in the schema, and the description provides sufficient context for a sandbox creation tool.

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 100%, so baseline is 3. The tool description does not add additional meaning to the parameters beyond what the schema already provides.

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 tool creates a test parcel in the Sandbox with no real-world effect, returns a parcelID, and is the entry point for the sandbox lifecycle. It explicitly distinguishes itself from the production tool delivery_create_parcel.

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 specifies that the tool is for delivery-service PARTNERS testing only, contrasts with production creation, and lists the subsequent tools that consume the returned parcelID, providing clear when-to-use and when-not-to-use guidance.

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