Deletes an image folder and all its contents recursively, with no undo option. Warn the shop owner before using to prevent permanent loss.
Delete an images folder WITH everything inside it, recursively. No undo - warn the owner first.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes |
Changes observed during successful MCP inspections.
v6.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and explicitly discloses the critical behaviors: recursive deletion and lack of undo. This goes beyond the minimal schema and appropriately warns the agent about the destructive 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?
Two short sentences with the primary action front-loaded and the warning second. No unnecessary words or repetition; every phrase earns its place.
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?
For a simple one-parameter delete operation with no output schema, the description covers the main behavior and irreversibility. The missing path format detail is a minor gap, but overall the description is sufficient for invoking the tool correctly.
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 description does not explain the path parameter's format, whether it must be absolute/relative, or any constraints beyond 'images folder'. With 0% schema coverage, the description should compensate, but it leaves the agent to infer path semantics.
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?
States a specific verb (Delete), resource (images folder), and scope (recursively), which clearly distinguishes it from sibling tools like engine_image_remove (single image) and engine_image_dir_add. The purpose is immediately obvious.
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 clear usage context by warning about the irreversible nature ('No undo - warn the owner first'), implying careful use. It does not explicitly name alternatives, but the operation is self-evident from the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.