Publish an image onto a Shopify product

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

Adds genuinely valuable context not present in annotations: server-side fetch, asynchronous processing, and the crucial clarification that a PROCESSING media status is success rather than failure. It does not address the annotation's destructiveHint=true or idempotentHint=false, so an agent gets no warning that repeated calls may create duplicate media entries.

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?

Front-loaded with the action and required inputs, then the async-status caveat, then eligibility and cost. Dense but every sentence carries operational information; nothing is padding.

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 3-param mutation with no output schema, the description covers inputs, eligibility, cost, and the async result behavior that would otherwise look like an error. The missing piece is any statement about what a repeat call does, given idempotentHint=false.

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 100%, so the baseline is 3, but the description still adds meaning: imageUrl must be a PUBLIC https URL, and productId must be in gid://shopify/Product/ form. The optional alt parameter is left to the schema.

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?

States a precise verb and resource: attach a finished image to a Shopify product listing as product media. It names the exact source of the ID and the required input forms, so it is unmistakable against siblings like list_shopify_products or set_product_image.

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?

Gives clear context for use (productId comes from list_shopify_products, imageUrl from any Hermoso render) and an explicit eligibility exclusion: only accounts created by installing Hermoso from the Shopify App Store. It does not name a competing sibling tool to route away from, so it stops short of 5.

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