update_inventory_product

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

Annotations provide idempotentHint=true, and description adds behavioral info: duplicate name rejection, name matching via ID or exact name, and category disambiguation. No contradiction with annotations.

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?

Two sentences with no fluff. First sentence states purpose, second adds key constraints. Information is front-loaded and every word earns its place.

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?

With output schema present and annotations, the description covers core functionality and constraints. Minor gap: does not mention product existence prerequisite or error handling. Still, sufficiently complete for moderate complexity.

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 descriptions are generic (just 'a string that will be trimmed'), but the description adds meaning: product accepts ID/name, category helps with duplicates. However, 'name' and 'newCategory' are not explicitly explained, leaving some ambiguity.

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?

Description clearly states 'Rename and/or move an inventory product' - specific verb+resource. It adds nuance about accepting ID or exact name and handling duplicates, distinguishing it from sibling tools like update_inventory_category or create_inventory_product.

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?

Provides context on when to pass category (when name may be duplicated) and notes duplicate rejection, but does not explicitly contrast with alternatives like create_inventory_product or other update tools. Lacks when-not-to-use guidance.

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