Delivery: create announcement [3PL]

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

Annotations indicate readOnlyHint=false, and description adds that it's a creation action on the delivery-service side. It also notes role restriction (403/404 on regular accounts) which is beyond annotation info. No contradictions; additional context on behavior is useful.

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?

Description is extremely concise—two sentences and a comparison. No redundant information, front-loaded with core purpose. 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 the complexity (9 parameters, nested objects, no output schema), the description covers the key contextual gaps: role restriction, comparison with parcel creation, and what the tool does. Could mention return value, but not essential. Overall well-rounded.

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 having a description. The tool description adds minimal parameter-specific info, but the high schema coverage means the description does not need to compensate heavily. 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?

Description clearly states it creates a shipment announcement between two 3PL services using specific verb 'creates' and resource 'announcement of a planned shipment'. It also explicitly distinguishes itself from sibling tool delivery_create_parcel, making its unique purpose clear.

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?

Provides explicit when-to-use: 'Use it when you need to notify the receiving party about an upcoming parcel handover'. Also gives context on who can use it (3PL accounts only, regular returns 403/404) and directly contrasts with delivery_create_parcel, offering clear alternative.

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