Доставка: отмена посылки [sandbox v1]

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

Description adds no behavioral insights beyond what annotations provide (non-readonly, non-destructive, non-idempotent). Does not explain side effects (e.g., state change, reversibility) or error conditions.

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?

Single sentence is under-specified. While concise, it omits critical information, making it insufficient for adequate tool understanding.

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?

Given the parameter count (4), complexity (nested object, external reference), and lack of output schema, the description is too sparse. It fails to provide necessary context for agent decision-making, especially regarding state, idempotency nuance, and sandbox limitations.

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 description coverage is 75%, but the tool description adds no parameter semantics. The required parcelID parameter is undocumented in both schema and description, and options relies on an external reference. DryRun and idempotencyKey are described in schema but not elaborated in description.

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 states it cancels a test parcel, but does not clarify the resource type or distinguish from sibling tools like delivery_sandbox_cancel_parcel or delivery_v1_cancel_announcement. It is clear but minimal.

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?

No guidelines provided. Does not indicate when to use this tool vs alternatives, prerequisites (e.g., parcel state), or context such as sandbox-only applicability.

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