delete_store_product_image

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, idempotentHint=true. Description adds value by stating 'Permanently delete' and 'cannot be undone', plus discloses authentication (API key), rate limits (max 10 concurrent requests), and that it respects read-only/dry-run modes. This goes beyond annotations.

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: concise first sentence, then context, then behavioral notes, then parameter docs, then return value. No redundant sentences. Every part adds value.

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 presence of an output schema, the description correctly summarizes return format. It covers purpose, parameters, behavior (irreversible, rate limits, auth), and return. No gaps for a delete operation.

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 has 0% coverage, but description provides detailed guidance for each parameter: source for store_id (list_ecommerce_stores), ownership for product_id, and account configuration (environment variables). This compensates fully and adds practical meaning.

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 it deletes an image from a product in an e-commerce store. This is specific and distinct from other delete tools in the sibling list (e.g., delete_store_product, delete_store_product_image). The verb 'delete' and resource 'store product image' are precise.

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 mentions irreversibility ('cannot be undone') and distinguishes between manual commerce writes and integrations (Shopify/WooCommerce auto-sync). This provides context on when to use the tool versus relying on automatic syncing. Could be improved by stating when not to use, but current guidance is clear.

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