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

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

The description indicates cancellation ('отмена'), which is a destructive mutation, but annotations set destructiveHint=false, contradicting the description. This contradiction (annotation_contradiction=true) severely undermines transparency. No additional behavioral details are provided.

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 very short (single line) and front-loads the sandbox context, but its brevity sacrifices informative content. It is concise but not optimally structured for clarity.

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 tool's complexity (4 params, nested object, no output schema, contradictory annotations), the description fails to provide necessary context. It omits behavior on cancellation, side effects, or how to interpret results, making it incomplete for an agent.

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?

All parameters have schema descriptions (100% coverage), but the description adds no extra meaning beyond mentioning actor. The parcelID description references an external file without clarifying the structure, which is insufficient. The description does not compensate for the opaque nested type.

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 the action ('отмена тестовой посылки' - cancel a test parcel) and the resource ('посылка'). The '[SANDBOX]' prefix indicates the environment. However, it does not differentiate from sibling tools like delivery_v1_cancel_parcel, which may cause confusion.

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 implies sandbox usage via the '[SANDBOX]' tag and mentions actor roles ('sender/receiver'), but does not explicitly state when to use this tool versus alternatives like delivery_v1_cancel_parcel or delivery_cancel_announcement_3pl.

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