update_inventory_item

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

With no annotations, the description carries the full transparency burden. It discloses the critical partial-update behavior and the side effect that brand, part_type, location, and vendor are auto-created if new. This is rich behavioral context beyond simple mutability.

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 opens with a clear one-sentence summary, then uses a structured 'Args:' list. For 13 parameters, the length is justified, and each line provides necessary semantics with no filler.

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 high parameter count and absence of annotations, the description covers purpose, update semantics, side effects, and parameter meanings. The output schema exists to explain return values, so the description need not detail them. Overall, it is sufficiently complete for an agent to use 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 must compensate. It lists all 13 parameters with concise, meaningful explanations (e.g., 'brand: Brand name (will be created if new)'), adding value beyond the schema's type information.

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 starts with 'Update an existing inventory item', using a specific verb ('Update') and resource ('inventory item') while explicitly stating 'existing'. This clearly distinguishes it from creation (add_inventory_item) and retrieval (get_inventory_item) tools.

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 usage by saying 'Update an existing inventory item' and explains the partial-update behavior ('Only the fields you provide will be changed'), giving clear context. However, it does not explicitly name alternatives or state when not to use this tool.

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