Delivery: parcel info [sandbox v1]

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. Description adds useful context: sandbox-only, works only with specific creation method, and returns info. No contradictions. Could mention error handling for invalid parcelID, but not critical.

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 concise sentences, no fluff, front-loaded with sandbox context, efficient use of 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 simple read-only getter with one parameter and full annotations, the description provides all necessary context: domain (sandbox), resource (parcel), limitation (only from specific creator). 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?

Only one parameter (parcelID) with schema description 'Test parcel identifier.' Tool description does not add semantic details beyond the schema, but context of 'test parcel in sandbox' is inferred. Baseline 3 as schema coverage is 100%.

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?

Description clearly states 'Returns information about a test parcel by parcelID', specifying verb, resource, and scope. The sandbox-only restriction and dependency on delivery_create_sandbox_parcel_v2 differentiate it from siblings like delivery_tracking and delivery_create_sandbox_parcel_v2.

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 (sandbox, test parcel by ID), when not to use (not outside sandbox, only for parcels created via delivery_create_sandbox_parcel_v2). Provides clear context and restrictions.

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