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

The description does not disclose side effects (e.g., whether the slide is appended or replaces existing ones), return values, or error behavior. Annotations indicate a non-read-only, non-idempotent, non-destructive operation, but the description adds little detail beyond the basic action.

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 repetitive, repeating the same phrase in the main text and the 'Guidance' portion, and ends with an unhelpful 'context' note. It could be condensed to a single clear sentence.

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 large set of sibling tools, the description does not provide enough context to help an agent decide when to select this tool over similar ones (e.g., shop_upload_product_pdf). It lacks information about the difference between uploading a slide vs. a PDF or updating a slide.

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 parameters (100% coverage), so the description does not need to add parameter details. The 'context' note in the description is redundant and does not enhance understanding 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 the action ('Upload an image file') and the target resource ('as a product slide'), and notes the multipart form-data format. This is specific enough to distinguish from related tools like shop_upload_product_pdf.

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 no guidance on when to use this tool versus alternatives such as shop_update_product_slide or shop_delete_product_slide. It also lacks any mention of prerequisites or common use cases.

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