⚠️ Delivery: create parcel [3PL]

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

Annotations already set readOnlyHint=false, so creation behavior is known. Adds context about error codes for regular sellers and production vs sandbox, but does not detail side effects, rate limits, or idempotency.

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 short sentences that front-load purpose, required fields, and key distinction. No wasted words.

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 complex schema and no output schema, the description omits return value, prerequisites, and any guidance on typical usage flow. For a creation tool with 12 parameters, this is too brief to be fully self-contained.

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 has 100% description coverage, so baseline is 3. The description only restates that required parameters are required (orderID, parcelID, items, sender, receiver, payment), adding minimal value beyond the schema. No clarification of parameter meanings or constraints.

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 'Production creation of a parcel on the delivery-service side', specifies required fields, and distinguishes from sandbox sibling. Verb+resource is specific and unambiguous.

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 contrasts with delivery_create_sandbox_parcel_v2 and notes that regular seller accounts get 403/404, implying it's for 3PL only. Could be improved with an explicit 'use this for production 3PL parcels only'.

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