product_update_inventory

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

With no annotations provided, the description partially fulfills the burden by indicating mutation ('Bulk-update'). However, it lacks details on atomicity, error handling, or batch behavior, which are critical for a bulk operation tool.

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 concise and well-structured with a clear purpose, parameter list, and example. Every sentence adds value, and there is no extraneous information.

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?

Given the presence of an output schema (not detailed here), the description adequately covers input semantics. However, it omits behavioral traits like idempotency or error responses, which would enhance completeness for a mutation tool.

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 input schema only defines 'data' as a string with no structure, but the description fully details the JSON array format, required and optional fields (sku, price, stock, specialPrice), and includes an example. This adds significant meaning beyond the schema, compensating for zero schema coverage.

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 'Bulk-update product price and/or stock (inventory sync),' clearly specifying the verb ('Bulk-update') and resource ('product price and/or stock'). It effectively distinguishes from sibling tools like product_create or product_update by focusing on inventory sync.

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 mentions 'inventory sync' but does not provide explicit guidance on when to use this tool versus alternatives (e.g., product_update). There is no indication of prerequisites or when not to use it, leaving the agent without clear selection criteria.

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