create_admin_maintenance_clean_recipe_folders

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

The description explicitly discloses the destructive nature of the operation ('Deletes'), which is critical since no annotations are provided. However, it does not elaborate on potential side effects, permissions required, or irreversibility.

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, well-structured sentence that conveys the core functionality without unnecessary words. It is front-loaded with the action and 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?

While the description covers the basic purpose, it omits scope (e.g., admin-only, system-wide), potential return values or success criteria, and error conditions. Given the tool's simplicity, the missing details leave some ambiguity for the agent.

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 only parameter (accept-language) is not mentioned in the description, and the input schema has 0% description coverage. The description adds no context about the parameter's purpose or usage, failing to compensate for the schema's lack of documentation.

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 all the recipe folders that don't have names that are valid UUIDs'. This provides a specific verb (deletes), resource (recipe folders), and condition (invalid UUID names), which distinguishes it from sibling cleanup tools like clean_images and clean_temp.

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 lacks any guidance on when to use this tool versus alternatives such as other maintenance cleanup tools. It does not mention prerequisites, frequency, or scenarios where this tool should be avoided.

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