update_store_product_image

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

Adds behavioral traits beyond annotations: authentication via API key, max 10 concurrent requests, respect for read-only/dry-run modes. Annotations only show readOnlyHint false, idempotentHint false, destructiveHint false, so description usefully supplements.

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 a brief overview, usage details, and parameter list. No redundant sentences; each sentence serves a purpose. Appropriate length.

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, partial update behavior, manual vs. automatic sync, authentication, rate limits, dry-run support, parameter explanations, and return type. Sufficient given tool complexity and lack of output schema details.

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?

With 0% schema description coverage, the 'Args' section explains all 5 parameters clearly, including how to obtain values (e.g., store_id from list_ecommerce_stores) and examples (additional_fields like url, variant_ids). Adds meaning beyond 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 'Update an image attached to a product in an e-commerce store', specifying the verb 'update' and the resource 'image'. It implicitly distinguishes from siblings like create_store_product_image (create) and get_store_product_image (read).

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?

Provides usage guidance: 'Only the fields you pass in additional_fields are changed' for partial updates, and explains when manual vs. automatic sync applies. Lacks explicit when-not-to-use or alternative tool names but context is clear.

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