update_product

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

No annotations provided, so description carries full burden. Discloses partial update behavior and that ARCHIVED status hides product but preserves order history. Lacks mention of authorization needs or reversibility, but provides good operational context for a mutation 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?

Two well-structured sentences. First sentence front-loads purpose and fields. Second sentence covers behavior and alternatives. No redundant words. Highly efficient.

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 no output schema and low schema coverage, description covers the tool's full scope: what it does, how to use it (partial update), effect of status, and pointers to other tools for related operations. Complete enough for correct invocation.

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 coverage is low (14% only for id and status enum). Description adds value by explaining partial update semantics and 'only send changed fields' pattern. Explicitly describes status options. Does not add details for other params beyond listing, but enough for core fields.

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?

Clearly states it updates core fields of an existing product, lists specific fields (title, description, vendor, productType, tags, status). Distinguishes from sibling tools like update_variants, upload_product_image, etc., by specifying what not to use it for.

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?

Explicitly advises to only provide fields to change, with omitted fields left untouched. Explains effect of status=ARCHIVED. Directs user to alternative tools for variants, prices, inventory, and images, giving clear 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.