get_store_product_image

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

Annotations already include readOnlyHint=true and destructiveHint=false. The description adds 'Read-only, safe to retry,' 'Max 10 concurrent requests,' and 'Authenticated via API key,' which are not captured by annotations. No contradiction.

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 well-structured: purpose, use case, limitations, argument list, and return value. Every sentence adds value without redundancy.

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 the tool has 4 parameters and an output schema, the description covers purpose, parameter sources, concurrency limits, and output shape (JSON with id, url, variant_ids). It lacks details on error handling or image size, but is sufficient for most use cases.

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 description coverage is 0%, but the description provides detailed argument explanations: store_id from list_ecommerce_stores, product_id, image_id from list_store_product_images, and account optional with default and configuration instruction. This adds substantial meaning beyond 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?

The description clearly states 'Retrieve a single image attached to a product in an e-commerce store' and 'Use to inspect one image's URL and variant associations.' It uses specific verbs and resources, and distinguishes from sibling tools like create, update, and delete image tools.

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 context: 'Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync product images automatically.' It also mentions authentication and concurrency limits, but does not explicitly state when not to use this tool versus alternatives.

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