delete_printer_files

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses irreversibility, the two-step dry-run confirmation flow with a returned code, what the dry-run response contains, and the print-running safety guard.

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 dense but front-loaded and well structured. It moves from purpose to selection criteria to the confirmation workflow and finally the safety warning, with every sentence contributing necessary information.

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 file-deletion tool with no annotations and no output schema, the description covers the critical missing context: destructive nature, confirmation protocol, response contents, irreversibility, and runtime blocking. An agent has enough information to call it safely and correctly.

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 0%, so the description must compensate. It explains names as values from printer_files, older_than_days as an age filter, and confirm as the code from the dry run. It gives kind values for prints and thumbnails but does not explicitly state the exact kind value for timelapse videos, leaving a minor gap on the required parameter.

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: delete files from the printer's SD card. It further distinguishes the supported file categories (timelapse videos, past prints, orphan thumbnails), making it clearly different from sibling delete_object, which operates on project objects.

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?

It explains how to select files, either by names from printer_files or by older_than_days, and gives a strong operational condition: nothing is deleted while a print is running. It does not explicitly name sibling tools or discuss when to prefer them, but the usage path is clear.

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