item_set_tracking_mode

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

Despite annotations declaring idempotentHint and destructiveHint, the description adds meaningful behavioral context: prerequisite checks, named error conditions, and the fact that no journal entry is posted. It does not explain idempotency-key behavior or the response, but it adds substantial value beyond the annotations.

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 wasted text. The core operation is front-loaded, followed by applicability constraints and the accounting note in a logical order.

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 mutation tool with no output schema, it covers the critical preconditions and error cases well and clarifies that no journal entry is posted. It is still missing expected success behavior or return information and idempotency-key semantics, but the operational picture is largely complete.

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 carry parameter meaning. It documents the mode values and ties itemId to the target item, but workspaceId and idempotencyKey are not explained, leaving clear gaps for a four-parameter required schema.

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 names a specific verb and resource: set an item's lot/serial tracking mode, and it explicitly enumerates the supported modes. This distinguishes the tool from sibling item, lot, and serial tools because it is the item-level tracking configuration 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?

It gives strong when/when-not conditions: the item must be stockable, on-hand must be zero for any non-none mode, and service/non-stockable items are not applicable. It also specifies the requirement for returning to none. It does not name sibling alternatives, but the operational conditions are explicit.

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