Delivery: cancel announcement [3PL]

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

Annotations already signal destructiveness; description adds emphasis on irreversibility and reveals authorization behavior (403/404 for regular sellers). No contradiction with annotations, but could detail more side effects.

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?

Three sentences are front-loaded with purpose, then key traits (irreversibility, prerequisite creator, authorization). No redundant words.

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?

No output schema is provided, and description does not explain return values or error states beyond the 403/404. It also lacks guidance on optional parameters (e.g., dryRun, idempotencyKey) and prerequisites beyond existence of announcement.

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 each parameter already described in detail. Description adds no additional parameter-level information, 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?

Description clearly states the action (cancel) and resource (announcement), explicitly ties to 3PL-specific creation tool, and distinguishes from siblings by noting its exclusive use for 3PL accounts and the 403/404 response for regular sellers.

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?

Description indicates usage context (cancelling a previously created announcement) and implicitly restricts to 3PL accounts via error mention, but does not explicitly compare with sibling cancel tools or state when NOT to use it.

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