create_store_product_image

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

Discloses that image_id must be unique within product and url must be publicly reachable. Annotations indicate it's a write operation (not read-only), and description adds context beyond annotations. However, doesn't specify behavior if image_id already exists (overwrite vs error).

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?

Well-structured with overview, parameter details in list, and return description. No superfluous content; every sentence adds value. Appropriate length for the complexity.

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 purpose, parameters, usage context, and return value. Output schema exists so return details are sufficient. Minor gap in not describing the 'account' parameter, but overall comprehensive for a creation tool.

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?

Adds meaning for 5 of 6 parameters (store_id, product_id, image_id, url, additional_fields) beyond schema. Provides examples and usage notes. Missing description for 'account' parameter, which is optional but still 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?

Clearly states 'Add an image to a product in an e-commerce store' with specific verb and resource. Distinguishes from siblings like delete_store_product_image and other store operations by specifying the action and context.

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 states when to use this tool for manual/custom stores versus when not (Shopify/WooCommerce sync automatically). Also provides prerequisite by mentioning how to obtain store_id from list_ecommerce_stores.

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