Delivery: cancel parcel [sandbox v1]

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

Annotations already mark as destructiveHint=true. The description adds context about the two-step process (initiate acceptance prohibition, then cancel) and the sandbox-only scope, which goes beyond what annotations provide. Does not discuss dryRun or idempotency, but these are partially covered in the schema.

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?

Three sentences, each providing essential information: purpose, prerequisite, and sibling distinction. No redundancy or unnecessary details.

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?

Covers purpose, scope, prerequisites, and key behavioral details. Lacks description of return values or error handling, but given the tool's sandbox context and no output schema, it is largely sufficient.

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 mentions 'options field' in the sibling comparison, but does not add significant meaning beyond the schema's own parameter descriptions.

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 cancels a test parcel in the sandbox, specifies the prerequisite (only parcels from delivery_create_sandbox_parcel_v2), and distinguishes it from a sibling tool (delivery_sandbox_cancel_parcel) by noting the v1 contract with an options field.

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 when to use this tool (sandbox only, for parcels created via a specific tool) and how it differs from delivery_sandbox_cancel_parcel, providing clear context for choosing between alternatives.

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