Delivery: bulk update [sandbox]

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

Discloses that the call only queues requests (async), sandbox context, partner-only requirement, and that it's implemented on the delivery-service side. No contradictions 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?

Five concise sentences covering purpose, usage, behavior, and parameter context without redundancy. Front-loaded with key info.

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?

Adequately describes the async batch nature and points to the result tool. Lacks immediate return value details, but reasonable given no output schema and sandbox context.

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%, but description adds value by explaining enum values, dryRun preview behavior, idempotencyKey duplicate protection, and the per-parcel nature of applications. The reference to external swagger is a minor weakness.

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 it queues a batch of parcel-property change requests, enumerates the specific types (changeReceiver, extendParcelStorage, etc.), and explicitly distinguishes from the single-parcel sibling tool delivery_v1_change_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?

Provides explicit guidance: use for bulk changes vs. single parcel via sibling tool; explains the queueing nature and that outcomes are reported via delivery_change_parcel_result; notes partner-only access restriction.

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