Delivery: create announcement [sandbox v1]

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

Annotations provide basic safety hints (readOnlyHint=false, destructiveHint=false). The description adds context: 'no real-world effect' matches non-destructive, and it explains the dryRun parameter (preview without API call) and idempotencyKey behavior (duplicate protection with conflict error). This goes beyond the structured data.

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 two sentences, front-loaded with the core purpose and effect. It efficiently includes usage guidance and behavioral context with no wasted words. Every sentence is necessary and well-positioned.

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 high schema coverage (100%) and no output schema, the description provides sufficient context: it clarifies the sandbox nature, distinguishes from sibling, explains dryRun and idempotencyKey, and gives usage boundaries. No gaps remain for effective agent decision-making.

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 100%, so the schema already describes all parameters adequately. The description mentions the options field difference but does not add substantial new semantic meaning beyond what's in the schema. Baseline 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 'Creates a test shipment announcement in the Sandbox (no real-world effect); returns a success status.' It specifies the verb (creates), resource (test shipment announcement), and context (sandbox). It also distinguishes from the sibling tool delivery_sandbox_create_announcement by noting the difference in 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?

The description explicitly advises to 'Use the base contract delivery_sandbox_create_announcement unless you specifically need this v1 shape' and explains the only difference (v1 requires options). It also notes the tool is 'Sandbox-only, for delivery-service PARTNERS,' providing clear when-to-use and when-not-to-use guidance.

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