receive_inventory_shipment

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

There are no annotations, and the description only says 'Receive items from an inventory shipment.' It doesn't disclose side effects (e.g., inventory updates, shipment status changes), permissions, or return behavior, leaving a significant gap for a mutating operation.

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 wasted words. It is appropriately front-loaded, though it lacks additional structure such as examples or elaborations that could enhance usefulness without bloating.

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, putting the burden on the description. It fails to explain what 'receiving' entails, what happens to the shipment status, inventory levels, or what the response will be. This is inadequate for a write operation with nested parameters.

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 basic descriptions for both parameters (shipmentId, lineItems). The tool description adds no extra meaning beyond the schema, but the schema itself provides adequate parameter-level context.

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 action ('Receive items') and resource ('inventory shipment'). It is specific enough to distinguish from generic inventory operations, though it doesn't explicitly call out sibling tools like receive_inventory_transfer.

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?

No guidance is provided on when to use this tool versus alternatives such as receive_inventory_transfer or create_inventory_shipment. The description simply states the function without contextualizing it within related inventory workflows.

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