Delivery: actual address [sandbox]

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

Annotations already indicate readOnlyHint=false (mutation), idempotentHint=false (non-idempotent), destructiveHint=false (not destructive). Description adds sandbox context, return value (empty 200), and partner-only restriction. Does not contradict annotations, but adds limited behavioral detail beyond the 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?

Two sentences plus a sibling reference, no wasted words. Essential information is front-loaded: action, context, partner restriction, and sibling distinction.

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 it's a sandbox tool with full schema coverage and annotations, the description covers purpose, return value, sibling distinction, and user restriction. Could mention that it is non-idempotent (though annotations indicate), but overall fairly complete.

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 description coverage is 100%, so the schema already provides parameter details. The description's phrase 'ACTUAL pickup point' aligns with the address parameter but adds no new meaning beyond the schema. 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?

Clearly states the tool sends the actual pickup point for a parcel's acceptance/return, and distinguishes from the sibling tool delivery_set_order_properties, which sets cost/parameters. The verb 'sends' and object 'actual pickup point' 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?

Provides clear context: needed for agent and customer returns, for delivery-service partners only. Distinguishes from sibling tool by purpose. Does not explicitly state when not to use, but the partner restriction and sibling differentiation give sufficient guidance.

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