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

With no annotations, the description carries the full disclosure burden and does well: it explains line splitting, that lot/custom fields are copied onto the new line, the accepted status values, and what is returned. It omits failure modes (invalid status string, quantity exceeding the line, missing unit) and any permission or irreversibility notes.

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?

Four tight sentences with the core action front-loaded and each subsequent sentence adding a distinct fact (split rule, valid statuses, return value). No filler, though the status enumeration could have been grouped more crisply with the split clause.

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 3-required-param mutation with no annotations and no output schema, the description covers the mutation's side effects and the return value, which is the hard part. The remaining gap is the unexplained unitId parameter and absent error/precondition guidance.

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 0%, so the description must compensate and only partly does: 'toStatus' is given its four valid values and 'quantity' is given meaning through the split rule. 'unitId' is never explained, and the text's framing as 'stock line' versus the parameter name 'unitId' leaves the identifier's target ambiguous.

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 gives a specific verb and resource ('Moves a quantity from a stock line to another status') and the split behavior makes clear this is a partial-quantity move rather than a whole-line status change. It never names the nearest sibling (set_inventory_unit_status), so the differentiation is left implicit.

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?

'Use this for partial ship/receive of a lot line' supplies a concrete triggering scenario, and the split rule tells the agent what happens when the quantity is smaller than the line. It stops short of stating when NOT to use it or which sibling to pick for a full-line status change.

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