create_inventory_shipment

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Create a new inventory shipment') without mentioning side effects, required permissions, or what the resulting shipment entails. There is no indication of return value or impact on inventory levels, making the tool behaviorally 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 a single, efficient sentence with no redundancy. It gets directly to the point, but is perhaps too terse to be fully helpful. Given the brevity, it earns a solid score for conciseness, though it could be expanded without losing focus.

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 no output schema and no annotations, so the description is the only source of contextual information beyond parameter names. It explains neither the return value nor any side effects or prerequisites. For a creation tool with conceptually similar siblings, the description is insufficiently complete for reliable agent selection.

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 has 100% description coverage for all four parameters, including nested line items, so the schema already documents parameter semantics. The description adds no extra meaning beyond what the schema provides, warranting the baseline score of 3.

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 identifies the action ('Create') and resource ('inventory shipment'), but it does not distinguish this tool from the sibling create_inventory_transfer, which is conceptually similar. The scope and specific meaning of 'inventory shipment' are not elaborated, so it lacks the full differentiation expected for a 5.

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 gives no guidance on when to use this tool versus alternatives. With sibling tools like create_inventory_transfer and receive_inventory_shipment, the absence of usage context leaves the agent to guess which operation is appropriate. No exclusions or preconditions are mentioned.

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