execute_order_shipment

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

No annotations provided, but description fully covers behavioral traits: it's a write operation, triggers customer notifications (depending on settings), requires shippable order state, and describes return structure (dict with success, resource_id, message). Discloses error condition for unshipable orders.

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?

Well-structured with clear sections: purpose, usage, API call, return structure, side effects. Every sentence provides value. No redundancy, and the information is front-loaded with the essential write indication and purpose.

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 simple write tool with one parameter and no output schema, the description covers return structure, side effects, and error conditions. Could mention potential partial shipment behavior or further constraints, but overall sufficiently 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 coverage is 100% with clear description '訂單 ID'. Description does not add extra meaning beyond the schema, but given the single simple parameter, no additional context is needed. Baseline score of 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?

Description starts with [WRITE] and clearly states it marks an order as shipped and triggers the Shopline shipment process. It distinguishes itself from siblings like cancel_order, update_order_status, and bulk_execute_shipment by specifying single-order write operation.

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 applicability: '適用於倉庫確認出貨後的狀態更新' (after warehouse confirms shipment). It notes the order must be in a shippable state, which is a key guideline. However, it does not explicitly mention when not to use or compare to alternative tools like bulk_execute_shipment.

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