Delivery: create announcement [3PL]

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

Annotations already indicate non-read-only, non-destructive, open-world, non-idempotent. The description adds that the tool is for 3PL accounts and returns 403/404 otherwise, which is important behavioral context. It also clarifies this is an announcement, not a parcel, distinguishing 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?

The description is concise (two sentences) with the most critical information front-loaded: purpose, applicability, and distinction from sibling. No extraneous text.

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 9 parameters with nested objects and no output schema, the description provides sufficient context about the tool's purpose, authorization constraints, and relationship to sibling tools. It lacks return value details but that is not required without output schema.

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 each parameter. The description does not add additional meaning beyond what the schema provides. For example, it mentions barcode and packages but the schema already describes them. 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 it creates an announcement of a planned shipment between delivery services, specifies it is for 3PL accounts, and distinguishes it from delivery_create_parcel by noting this is a shipment announcement, not parcel creation. The verb 'creates' and resource 'announcement' are specific.

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 states when to use ('notify the receiving party about an upcoming parcel handover') and what not to use (unlike delivery_create_parcel for parcel creation). It also notes the tool is for delivery-service side and returns 403/404 on regular seller accounts, providing clear usage context.

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