update_store_product

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

Annotations already cover behavior (readOnlyHint false, etc.). Description adds manual-write context and return format, but lacks details on side effects, validation, or error handling.

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?

Description is well-structured with purpose first, then usage context, parameter list, and return. No fluff, though could be slightly more concise.

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?

Covers the key intent, partial update behavior, examples of updatable fields, and return value. Could mention behavior for invalid fields or impact on synced stores, but overall adequate.

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?

With 0% schema coverage, description explains store_id, product_id, and additional_fields with examples. However, the 'account' parameter is missing from the description, leaving it undocumented.

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 'Update an existing product's ... metadata' and specifies partial update via additional_fields. However, mentioning 'images' as a field creates potential confusion with sibling tool update_store_product_image, slightly reducing clarity.

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 that manual writes suit custom/headless storefronts vs automatic syncs, but does not explicitly differentiate from related tools like create_store_product, update_store_product_image, or update_store_product_variant.

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