create_delivery_from_order

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

The description adds no behavioral context beyond what the annotations already convey (readOnly=false, destructive=false). It does not disclose side effects such as whether the delivery is drafted or issued, whether the order status changes, or what happens to existing positions. Since annotations already indicate it is a write operation, the description contributes minimal transparency.

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 a single, concise sentence with no unnecessary wording. It is appropriately sized for such a simple tool, though it lacks detail. The structure is easy to scan and understand.

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?

The description is too terse to be fully complete. With no output schema, it does not explain return values, and it omits information about the creation process or side effects. The schema and annotations cover parameters and safety hints, but contextual details like what happens after creation are missing.

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 input schema provides 100% coverage for both parameters, including a useful note about omitting positions to use all order positions. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 'Create delivery from order' uses a specific verb ('create') and names both the resource ('delivery') and source ('order'), making the core purpose unambiguous. However, it does not explicitly distinguish itself from sibling tools like issue_delivery or create_invoice_from_order, limiting differentiation.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. Users are left to infer that it is for converting an order into a delivery, but no explicit context or comparison with siblings is provided.

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