⚠️ Delivery: create parcel [3PL]

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds value by stating the tool creates a real parcel in production, is implemented by a partner, and returns 403/404 for regular accounts. No contradiction with annotations.

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 (two sentences) and front-loaded with the main purpose. Every sentence adds value: purpose, implementation/error context, and sibling differentiation. 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?

For a complex tool with 12 parameters, nested objects, and no output schema, the description covers purpose and access restrictions but does not explain the expected output or behavior on success. 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% with descriptions. The description reiterates the required parameters (orderID, parcelID, items, sender, receiver, payment) but does not add semantic meaning beyond what the schema provides. Baseline score maintained.

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', specifying the verb 'create' and resource 'parcel'. It distinguishes from the sibling 'delivery_create_sandbox_parcel_v2' by explicitly contrasting production vs sandbox.

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 contrasts with the sandbox sibling, indicating when to use this production tool. It notes that regular seller accounts get 403/404, implying it's for specific accounts, but doesn't provide explicit when-not-to-use guidance beyond that.

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