Update inventory

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

The description discloses that the update uses an 'ABSOLUTE' value setting, which is a key behavioral trait. However, it does not explain side effects (e.g., overwriting existing quantities), validation rules, or any error conditions. With no annotations, the description carries the burden but only partially addresses it.

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 a single, front-loaded sentence that conveys the core purpose efficiently. It is concise and free of fluff, though it could add valuable details without becoming verbose.

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 tool has a non-trivial parameter (array of objects) and no output schema, yet the description provides minimal context. It does not explain expected input format, return values, or preconditions, making it incomplete for an agent to use confidently.

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?

The schema coverage is 0%, and the description provides no information about the 'updates' parameter or its structure. The schema defines a complex array of objects, but the description does not help an agent understand how to construct the updates, leaving a significant 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 clearly states the verb 'update' and the resource 'inventory quantity', with the scope 'per variant' and 'ABSOLUTE' setting. This distinguishes it from other inventory-related siblings like rms_get_inventory or rms_upsert_variant_inventory.

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 implies a specific use case (absolute value updates per variant) but provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or point to any sibling tools.

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