Delivery: create parcel [sandbox]

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

Disclosures include no real-world effect, no consequences, and return of parcelID. Aligns with annotations (readOnlyHint=false implies write operation, destructiveHint=false supports no consequences).

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?

Concise two-sentence structure: first sentence defines purpose and return, second provides comparison and usage context. No redundant information.

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?

Given complexity (7 optional parameters, nested objects, no output schema), the description covers sandbox scope, lifecycle, target audience, and key return value fully. Enough for agent to decide and invoke.

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% with parameter descriptions. The tool description does not add significant parameter-specific detail but provides context about the sandbox lifecycle and return value.

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 parcelID, and distinguishes it from the production sibling 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?

Explicitly states 'For delivery-service PARTNERS testing only', contrasts with production creation, and identifies it as the entry point for a sandbox lifecycle with links to subsequent tools.

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