inventory-set-quantities

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

With no annotations provided, the description does useful work: it explains that quantities are absolute, describes the conditional changeFromQuantity behavior and resulting CHANGE_FROM_QUANTITY_STALE error, and explains idempotency retry semantics. It still omits permission requirements and whether the whole batch is atomic.

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?

Three sentences, front-loaded with the core operation. Each sentence adds useful information about use cases, conditional safety, and return/retry behavior without waste.

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 description covers the mutation's key behavior and compensates for the lack of an output schema by mentioning idempotencyKey and userErrors. It is still missing some operational context, such as permissions and batch atomicity, which matters for a mutation tool with no annotations.

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 100%, so the schema already fully documents parameters such as changeFromQuantity and idempotencyKey. The description reinforces the conditional check and retry behavior, but adds little parameter meaning beyond the 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 states a specific verb and resource: 'Set absolute inventory quantities for items at specific locations.' This is precise enough to distinguish it from sibling read tools such as get-inventory-levels and get-inventory-items.

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 clear usage context with 'Use for inventory corrections, cycle counts, etc.' However, it does not name when not to use it or explicitly compare it with alternatives, and 'etc.' leaves the scope somewhat open.

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