Delete All Images

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does well by warning that the tool is disabled in read-only mode, that it commits an edit, and that it requires a two-step preview/confirm process.

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 convey the action, scope, and critical behavior without any waste. The main action is front-loaded, and the important constraints follow immediately.

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 destructive, multi-step tool, the description covers the key operational requirements: read-only limitation, preview-then-confirm flow, and the commit behavior. Required parameters and confirmation-token semantics are already documented in the schema, and an output schema exists, so the description is sufficiently complete.

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%, with detailed parameter descriptions for language, image_type, package_name, confirm, and confirmation_token. The description adds only minimal parameter-level context, so the baseline of 3 is appropriate.

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 states a specific verb and resource: deleting all store-listing images for a given language and image type. It clearly distinguishes this from sibling tools like delete_image (single image) and delete_all_listings (all listings).

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 gives clear operational context, including that the tool is disabled in read-only mode and requires a preview-then-confirm flow. It does not explicitly name alternatives or exclusion conditions, but the intended use is reasonably clear.

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