Publish an image onto a Shopify product

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses critical asynchronous behavior: Shopify processes the image server-side, so a PROCESSING status is success, not failure. It also explicates an account eligibility constraint and cost-free nature. This adds significant value beyond what annotations convey, with no contradictions.

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 is compact and front-loaded: the core action is stated in the first clause, followed by key parameter guidance, then critical async behavior, and finally constraints. Every sentence contributes essential information without repetition or fluff.

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?

For a mutation tool with no output schema, the description covers the essential operational context: how to identify parameters, what async processing means, success criteria, and eligibility. It lacks details about the response structure (e.g., whether a media ID is returned) but given the async nature and that the agent mainly needs to know success, this is adequate. Minor gaps prevent a 5.

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?

The schema already provides full descriptions for all three parameters (100% coverage). The description adds minimal extra meaning: it reaffirms that imageUrl should be a public https URL (already in schema) and clarifies that productId comes from list_shopify_products (also in schema). The alt parameter is not elaborated further. Baseline 3 is appropriate since the schema carries the explanatory load.

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 clearly states the verb 'Attach' and resource 'finished image to Shopify product listing as product media'. It uses specific language that distinguishes it from general publish tools, naming the exact target resource (Shopify product listing). This differentiates it from similar sibling tools like set_product_image which may have broader scope.

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 provides operational constraints (pass productId from list_shopify_products, use public https imageUrl, only for Shopify App Store installs) but does not explicitly state when to use this tool versus alternatives. It does not mention when not to use it or name alternative tools for similar tasks, such as set_product_image. Guidance is implied but not explicit.

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