delete_all_images

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

With no annotations, the description carries the full burden. 'Delete' and 'commit the edit' convey destructive and persistent behavior, and the read-only mode note provides a constraint. However, it does not disclose irreversibility, permission requirements, or side effects on published listings, which would be valuable for a bulk delete operation.

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 two sentences, front-loaded with the primary purpose, and includes a necessary behavioral note. There is no redundant or filler content, making it highly concise and well-structured.

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?

The description covers the key action and constraint (read-only mode), while parameter details are fully in the schema and output schema exists. It is adequate for a straightforward bulk delete tool, but could be enhanced with an explicit warning about the irreversible nature of deleting all images.

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 description coverage is 100%, and the tool description does not add extra parameter semantics beyond what the schema already provides. The description mentions 'language and image type' but these are already clearly defined in the schema, so no additional value is added.

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 ('Delete'), the resource ('all store-listing images'), and the specific scope ('for a language and image type'). This distinguishes it from the related sibling tool 'delete_image' which deletes a single image. The purpose is unambiguous.

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 implies usage for bulk deletion of all images of a given type, and notes that it is disabled in read-only mode. However, it does not explicitly compare to delete_image or state when not to use it. The guidance is clear enough for most cases but lacks explicit exclusions.

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