Delivery: create announcement [sandbox]

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

The description adds behavioral context beyond annotations: it discloses that the sandbox has no consequences, that the announcement is routed to the receiver's delivery service, and that it's a test environment. Annotations indicate non-readonly, non-idempotent, non-destructive, but description enriches understanding.

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 with three short sentences. It front-loads the main action, then specifies audience and distinguishes from sibling. No superfluous information.

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) and no output schema, the description adequately explains the purpose and basic flow (creation and routing). It lacks detail on response or error handling, but for a sandbox tool the description is sufficient.

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%, so baseline is 3. The description adds overall context about what the announcement is (planned shipment) and routing, but does not provide additional per-parameter semantics beyond what the schema already documents.

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 the tool creates an announcement of a planned shipment in the test environment, using specific verbs and resource. It distinguishes from the sibling tool delivery_create_announcement_3pl by explicitly labeling this as sandbox.

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 says it is for delivery-service partners only and contrasts with the production version (delivery_create_announcement_3pl) noting this is a sandbox with no consequences, guiding when to use it.

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