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

No annotations are provided, so the description carries full responsibility. It discloses a critical limitation (not a retailer certification, verify in portal) and describes the output content. Nevertheless, it does not state whether the operation is read-only or has side effects, nor does it mention any prerequisites like required permissions or data freshness, leaving some behavioral aspects opaque.

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 three concise sentences: the first defines the output, the second lists integration targets, and the third states a caveat. Every sentence adds value, and the content is well structured, making it easy to parse and act on.

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 tool has moderate complexity with 4 parameters and no output schema. The description covers the output's key elements and provides integration context and a caveat, which is sufficient for an agent to select and invoke the tool correctly. It does not detail every possible return value, but the summary of output content is adequate.

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 detailed descriptions for all parameters, so the baseline is 3. The tool description adds context about what the output contains (e.g., which SKU, where, order, orientation, securing list, declarable figures) and mentions the optional per-retailer check, which helps understand parameter intent. However, it does not elaborate on parameter formats beyond what the schema already provides.

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 tool's function: exporting a load as a machine-readable loading work order with specific components (stuffing sequence, securing actions, declarable figures, retailer check). It distinguishes itself from siblings by specifying the exact output format and integration targets (WES/TMS, robotic palletiser, worker sheet), making its purpose unambiguous.

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 clear usage context: it is for generating loading work orders to meet retailer/carrier specs, and it explicitly warns that it is not a certification and to verify in the portal. However, it does not explicitly mention when to use this tool over alternatives like plan_load or export_dg_paperwork, so it lacks a direct comparison.

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