Create Inbound Delivery

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

Annotations already provide readOnlyHint=false and destructiveHint=true, so the description adds the creation behavior and required PO reference context. It does not disclose authorization needs, error conditions, or success responses, but is adequate for a creation tool.

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: first states purpose, second lists requirements. No unnecessary words, front-loaded, efficient.

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 tool with 4 parameters, nested objects, no output schema, and no error handling hints, the description covers creation from a PO but omits success output (e.g., delivery number) and failure cases. Annotations indicate destructiveHint=true, which seems contradictory, but description itself is moderately 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 baseline is 3. The description restates required fields and ties them together (e.g., items need referenceSDDocument and referenceSDDocumentItem), adding minimal extra meaning over 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?

The description clearly states the action ('Create') and the resource ('inbound delivery'), with the key prerequisite ('with reference to a purchase order'), which distinguishes it from siblings like s4_inbound_delivery_update or list tools.

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 lists required fields (shippingPoint, supplier, items with PO reference), giving clear context for when to use the tool. However, it does not explicitly exclude use cases or mention alternatives like s4_inbound_delivery_update for editing.

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