Delivery: push tracking event [sandbox]

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

Goes beyond annotations by describing non-modification of history, single transition per call, duplicate behavior, return status (empty 200, 4xx meaning), and retry policy. No contradiction with annotations.

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?

Single paragraph efficiently conveys purpose, usage, behavior, constraints, audience, and sibling differentiation. No wasted words, well-structured.

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 10 parameters, nested objects, and no output schema, the description adequately covers return values, error handling, retry policy, and audience. Idempotency key and dry run are described in schema, and description provides enough behavioral context.

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% parameter description coverage. The tool description adds valuable context like a status transition example (RECEIVED_AT_TRANSIT_TERMINAL → IN_TRANSIT) and idempotency implications, though individual parameters are sufficiently documented in schema.

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 appends one tracking event, does not modify history, and specifies it is only for appending status events, differentiating from siblings like delivery_set_order_properties and delivery_change_parcels.

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 when to use ('report movement as it happens'), what not to do (not idempotent, don't re-send same event), and differentiates from alternatives. Also mentions audience (delivery-service partners only) and retry policy.

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