Delivery: cancel announcement [sandbox v1]

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds minor context: 'starts the process' implying potential async behavior, and 'on success the response has a success status' (obvious). No additional behavioral traits disclosed beyond what annotations provide.

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 sentences are concise and front-load the key information (sandbox, cancellation, success status). Minor redundancy with '[SANDBOX v1]' prefix could be integrated better, but overall efficient.

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?

With no output schema, the description should give more detail on return values beyond 'success status'. Also lacks guidance on error cases or side effects. Given the tool's simplicity and 5 parameters, the description is minimally adequate but has clear gaps.

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 has 100% coverage of parameter descriptions, including the nested options object. The description only mentions 'required options field' without adding meaning beyond the schema. Baseline 3 is appropriate as schema does the heavy lifting.

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 cancels a test announcement in the sandbox, using specific verb 'cancelling' and resource 'test announcement'. It distinguishes from sibling tool delivery_cancel_announcement_3pl by noting sandbox vs production and different contract versions.

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?

Explicitly states availability only in Sandbox for delivery-service partners and contrasts with the production alternative. However, it does not provide explicit when-not-to-use scenarios beyond the environment restriction.

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