products_update_inventory

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

The description only says 'Update Inventory' which implies a write operation, consistent with readOnlyHint=false. However, it adds no detail about side effects, partial updates, required fields, or response behavior. With annotations covering the read/write nature partially, the description adds minimal behavioral context beyond the name.

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 extremely brief (two words) but this is under-specification rather than efficient conciseness. It lacks essential details such as what 'items' should contain, the purpose of altId/altType, and any warnings. A concise effective description should convey necessary information without fluff; this does not.

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 write tool that updates inventory with an array of items, the description provides no context about the structure of items, expected values, or consequences. Without an output schema, the agent has little guidance on what to pass or what to expect. The complete lack of detail makes the tool hard to use 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?

The input schema has 100% coverage with descriptions for all three parameters (altId, items, altType), including defaults. The tool description contributes zero additional parameter meaning. According to the rubric, when schema coverage is high, a baseline of 3 is appropriate; the description adds nothing but does not detract.

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 'Update Inventory' is a near-tautology of the tool name 'products_update_inventory'. It does state a verb and resource ('update' + 'inventory') but is extremely generic and does not specify what kind of inventory, which products, or what the update entails. It also fails to distinguish this tool from siblings like products_bulk_update or products_get_list_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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or exclusions. An agent has no information to decide between this and other product update tools.

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