item_set_tracking_mode

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

There are no annotations, so the description carries the full disclosure burden. It states that this is plain master data and posts no journal entry, and it reveals the constraint-heavy consequences of switching modes. This goes well beyond what the bare schema or annotations would provide.

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 dense but efficient: it front-loads the operation and mode values, then gives preconditions/errors, revert requirements, and side-effect disclosure in three short follow-up sentences. Every sentence earns its place.

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?

With no annotations and no output schema, the description covers purpose, valid modes, prerequisites, error codes, and the no-journal-entry side effect. The main omissions are explicit semantics for idempotencyKey and what a successful response contains, but these are not critical for invoking 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 is the only source of parameter meaning. It fully documents the mode parameter with exact allowed values and links it to item state. itemId is naturally implied, but workspaceId and idempotencyKey are not explicitly explained, leaving a minor gap.

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 resource: 'Set an item's lot/serial tracking mode,' followed by the four legal values. This clearly distinguishes it from sibling inventory/item operations like serial_set_status or update_item, which target different concerns.

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 explicit usage conditions: the item must be stockable (track_stock true), on-hand must be 0 for non-none modes, service/non-stockable items are rejected, and reverting to none requires all lots/serials archived and balanced. It even names the relevant error codes, letting an agent predict failure before calling.

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