Create Admin Maintenance Clean Recipe Folders

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

With no annotations, the description carries the full burden. It clearly discloses bulk destructive behavior with 'Deletes all' and defines the selection criterion, but it doesn't mention permanence, admin permission requirements, or whether folder contents are removed along with the folders.

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, front-loaded, waste-free sentence. Every word contributes to identifying the action, target, and filtering condition.

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 low-complexity tool with an output schema, the core selection criterion is adequately stated. However, because this is a destructive bulk delete with no annotations, an agent would benefit from knowing whether the deletion is irreversible, whether contents are deleted, and whether admin authorization is assumed.

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 schema has only one parameter, accept-language, with zero description coverage, and the tool description does not mention it at all. The low coverage is not compensated, though the parameter is an optional standard header, which limits the practical 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 states a specific verb ('Deletes'), a specific resource ('recipe folders'), and a precise condition ('names that are not valid UUIDs'). This clearly distinguishes the tool from sibling maintenance operations like cleaning images or temp 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 clear: this is an admin maintenance cleanup that removes invalidly named recipe folders. It doesn't explicitly discuss alternatives or exclusions, but the narrow resource scope makes when-to-use straightforward and no sibling tool performs the same operation.

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