Delivery: prohibit acceptance [sandbox]

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

Annotations declare destructiveHint: true, idempotentHint: false, readOnlyHint: false. The description adds that it returns a success status, is implemented on the delivery-service side, and that regular sellers receive 403/404. This adds behavioral context beyond annotations. No contradiction.

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 concise with three sentences that front-load the main action. It avoids unnecessary words and uses clear language. Every sentence provides useful information.

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?

The description covers the tool's purpose, usage context, and access limitations. It mentions it returns a success status but does not specify the response structure. Given the tool's simplicity and missing output schema, this is adequate for an agent to use it correctly.

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% with detailed parameter descriptions for dryRun, orderId, and idempotencyKey. The tool description does not add any additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 tool's action: 'Prohibits the delivery service from accepting a parcel from the sender — the parcel will not be taken into processing.' It also positions it as a step in the parcel-cancellation flow and distinguishes from siblings by specifying it's for delivery-service PARTNERS only.

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 provides usage context by mentioning it's a step in the parcel-cancellation flow and pairs with delivery_sandbox_cancel_parcel. It also explicitly states that regular seller accounts get 403/404, guiding who should use it. However, it does not explicitly list when not to use it or compare to other tools.

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