bulk_execute_shipment

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

No annotations provided; description discloses API call, side effects (batch update, partial failure, customer notifications), and return structure, compensating well.

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 sections for purpose, API, return, side effects. Front-loaded and concise, no superfluous text.

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 key aspects: batch operation, potential partial failures, return format. Sufficient for correct agent invocation given tool complexity.

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?

Single parameter order_ids with 100% schema coverage; description adds context of batch usage but no extra semantics beyond the 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?

Clearly states it's a write operation for batch executing multiple order shipments, distinguishes from single-order execution. The title and description specify the action and resource.

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?

Describes use case for daily batch shipment but lacks explicit when-not-to-use or comparison with sibling execute_order_shipment for single orders.

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