Delivery: set parcel properties [sandbox]

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

Annotations already declare destructiveHint=true (modification) and idempotentHint=false. The description adds that it is idempotent by overwrite (replaces previous values), returns empty 200, and is partner-only. This provides important behavioral nuance beyond 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 sibling clarification front-load the essential information. No wasted words; 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?

Covers purpose, usage constraint (partner), behavioral nuance (overwrite, empty response), sibling differentiation. Missing explicit mention of required authorization or the structure of orderId/properties, but schema handles that. Adequate given tool simplicity.

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 descriptions, so baseline is 3. The description adds critical usage guidance: always send the complete current set (not a delta) because each call overwrites. This is key for using the 'properties' parameter correctly.

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 sets a parcel's delivery parameters, gives an example (final delivery cost), and distinguishes from siblings (real address, tracking). The verb 'sets' and resource 'parcel's delivery parameters' 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?

Explicitly states it is for delivery-service PARTNERS only (not regular sellers), provides sibling alternatives (delivery_set_order_real_address, delivery_tracking), and clarifies always send complete set (not delta).

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