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 state read-only behavior, the cloud-mode connectivity requirement, sort order (newest first), and what is returned. It doesn't cover what happens if the printer is offline or how `limit` affects results, so some behavioral ground is left uncovered.

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?

Two compact sentences, front-loaded with the return shape and folder semantics; each parenthetical earns its place by defining a category. Slightly dense phrasing ('name, size and date and the total per folder') but no wasted content.

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?

There is no output schema, so the description must describe results, and it does (name, size, date, per-folder totals, sorted newest first). The one real gap is pagination/limit behavior for a list tool that caps at 30 by default.

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 entirely. It effectively defines the `kind` values via the three folder categories, but `limit` is never mentioned despite having a default of 30, and it doesn't clarify that 'all' is a valid kind.

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?

States the resource (files on the printer's SD card) and the returned fields (name, size, date, per-folder totals) plus sort order, which clearly separates it from siblings like delete_printer_files or download_printer_file. The verb is implicit ('Files on...' rather than 'List files'), but the enumeration of the three folder categories makes the scope unambiguous.

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 parenthetical definitions of timelapse/prints/thumbnails implicitly guide selection of the `kind` value, and 'works with the printer in cloud mode' gives a prerequisite. However, it never names alternatives (download_printer_file, delete_printer_files) or states when to prefer them, so usage is implied rather than explicit.

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