Delivery: actual address [sandbox]

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

Annotations already indicate a non-destructive write operation. The description adds that it returns an empty 200 on success, and the sandbox context implies safety. It also describes the dryRun and idempotencyKey parameters for additional transparency. However, it does not cover error scenarios.

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 very concise: one sentence for the main action, one for the return, one for sibling differentiation, and one for audience. It is front-loaded with essential information, no waste.

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?

For a tool with 4 parameters, 2 required, nested objects, and no output schema, the description provides the return type (empty 200) and links to a sibling. It explains the sandbox environment and parameter options. Missing error details but sufficient for a sandbox tool.

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?

The description supplements the 100% schema coverage by explaining the purpose of dryRun (preview without side effects) and idempotencyKey (duplicate protection). It does not repeat schema details but adds context for effective parameter use.

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 that the tool sends the actual pickup point address for parcel acceptance/return, distinguishes it from sibling delivery_set_order_properties (which sets cost/parameters), and specifies the intended audience (delivery-service partners only).

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 when to use it ('needed for agent and customer returns'), differentiates it from the sibling, and restricts usage to delivery-service partners (not regular sellers). This provides clear guidance.

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