⚠️ Delivery: create parcel [3PL]

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

Annotations are basic (readOnlyHint false, etc.). The description adds valuable context: it is a real parcel creation, and regular accounts get 403/404. This goes beyond annotations without contradicting them.

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 two sentences that front-load the key purpose and then provide usage context. Every sentence earns its place with no fluff.

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 complex nested parameters, but schema descriptions are thorough. The description does not explain return values (no output schema) or provide behavioral details beyond basic permissions. Adequate but could be more 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 baseline is 3. The description lists required parameters by name but adds little beyond the schema, only noting version stamps on dryRun and idempotencyKey.

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 parcel in production, with a specific verb and resource. It distinguishes itself from the sandbox sibling (delivery_create_sandbox_parcel_v2) by noting it is 'production, the creation of a real 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 explicitly indicates this is for production use, not for regular seller accounts (which get 403/404), implying 3PL accounts. It lists required parameters and contrasts with the sandbox version, providing clear when-to-use guidance.

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