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

Annotations already indicate destructive action (destructiveHint=true), and the description aligns with that. No additional behavioral details are provided, such as permanence or side effects, but the annotation lowers the bar for this dimension.

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 very short but includes redundant text ('Guidance: Deletes a specific product slide. | context: product_id, slide_id') that repeats the first sentence. This lack of clean structure reduces the effectiveness of the concise wording.

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?

There is no mention of expected outcomes, errors, or side effects beyond deletion. For a destructive operation, more context about what happens to the product or related media would improve completeness, even though no output schema is required.

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 provides descriptions for both parameters ('Slide Unique ID' and 'Product Unique ID'), so coverage is high. The description adds no extra meaning about the relationship between the IDs or how they identify the slide, but the schema is sufficient for basic understanding.

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 ('Deletes') and the object ('a specific product slide'), which distinguishes it from update/upload slide tools. However, it could more explicitly differentiate it from the broader set of delete 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?

There is no guidance on when to use this tool versus alternatives like shop_update_product_slide or shop_upload_product_slide. The description merely repeats the action without contextual direction.

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