Delivery: create announcement [sandbox v1]

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

Disclosures: sandbox-only, no real-world effect, returns success status. Annotations already indicate non-readOnly and non-destructive. Description adds context but could mention more about side effects or reversibility.

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, front-loaded with purpose and scope. No waste; every sentence adds value.

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 complexity (10 params, nested) and no output schema, the description covers key context: sandbox, partnership, and sibling differentiation. Could elaborate on return value details but sufficient for a test tool.

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 descriptions for all parameters. The description adds minimal param info beyond the schema, only highlighting that v1 requires the options field. Baseline 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 it creates a test shipment announcement in the Sandbox with no real-world effect. It distinguishes itself from the sibling tool delivery_sandbox_create_announcement by noting the v1 shape requires the 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?

Explicit usage guidance: use the base contract unless v1 is specifically needed due to the options requirement. Also specifies sandbox-only and for delivery-service PARTNERS.

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