lot_create

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

With no annotations present, the description carries the behavioral disclosure burden. It reveals important non-obvious behaviors: number uniqueness rules, error conditions like lot_number_taken and tracking_not_applicable, the default status, and the fact that on-hand quantity is derived from movements. It does not mention idempotency behavior or permissions, but the key behavioral traps are covered.

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 dense sentences with no filler. It front-loads the core action, then efficiently covers preconditions, optional parameters, and the critical quantity caveat.

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 9-parameter tool with no output schema and no annotations, this description covers the non-obvious inventory semantics and required preconditions well. The main omissions are idempotencyKey behavior and any indication of return value, but an agent still has enough context to invoke the tool correctly.

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 0%, so the description must compensate by explaining parameters. It adds real meaning: number length and case-insensitive uniqueness, optional fields, and default status. workspaceId and idempotencyKey are not explained beyond the schema, so the compensation is strong but not complete.

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 opens with a specific verb and object: 'Create a lot (a batch) against a lot-tracked item.' It clearly scopes the operation and is distinct from siblings like lot_update, lot_set_status, and lot_archive because it is explicitly the creation operation.

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 clear context for when to use the tool: when creating a lot for a lot-tracked item, and it explicitly states the precondition that the item must be lot-tracked. It does not name alternative tools such as serial_create or lot_set_status, so it stops short of full when-not/alternative routing.

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