Unbenutzte Bilder löschen

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It includes a 'VORSICHT!' warning that signals destructive potential and specifies the condition 'nicht verwendet' (unused). However, it does not explain the force parameter, whether deletion is permanent by default, or potential side effects such as broken references, leaving notable gaps.

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 a single sentence that is front-loaded with the primary action and includes a critical caution flag. It contains no filler or redundant explanatory content beyond what is necessary for the warning.

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?

As a destructive tool with no annotations and no output schema, the description is too minimal. It lacks context about how 'unused' is determined, the effect of the force flag, recovery options, and safe invocation workflow (e.g., using image_find_unused first). This is a significant gap for a deletion operation.

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 input schema provides 100% parameter coverage, including descriptions for mediaIds and force. The tool description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance parameter 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 tool deletes unused images, matching the name and title. It specifies the verb (löscht), resource (Bilder), and condition (nicht verwendet), and distinguishes it from the sibling image_find_unused which only locates unused images.

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 the tool is for deleting images that are no longer used, but it does not explicitly state when to use it versus alternatives like image_find_unused. No prerequisites or exclusion scenarios are mentioned, so the guidance is only implied.

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