Create Admin Maintenance Clean Images

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

With no annotations, the description takes on the safety burden and does disclose a destructive operation ('purges ... from the filesystem') and its exact criterion (non-.webp images). It does not explicitly say the deletion is irreversible or what happens to database references, but 'purges' and the filesystem scope make the destructive behavior clear.

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?

A single 11-word sentence that front-loads the verb and target and contains no filler. Every word 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 destructive no-required-parameter admin tool, the core action and scope are stated, and an output schema exists to describe return values. Missing side-effect detail such as permanence, permission requirements, and whether referenced images are also removed leaves a meaningful gap.

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 coverage is 0% and the description does not mention the optional accept-language parameter. The description adds no meaning about parameters; however, the only parameter is a standard optional HTTP header, so the omission is low-impact.

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 opens with the specific verb 'Purges' and names a concrete target: all filesystem images not ending in .webp. This clearly distinguishes it from sibling maintenance tools like create_admin_maintenance_clean_temp and create_admin_maintenance_clean_recipe_folders.

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 intended use is inferable from the action and the admin-maintenance sibling context, but the description never states when to prefer this tool over other cleanup tools or mentions any prerequisites or exclusions. It relies on the reader to connect 'clean images' with the desired maintenance goal.

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