cleanup

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

No annotations are provided, so the description carries the burden. It discloses the destructive nature ('Delete') and the risky default (deletes all), but does not mention permanence, reversibility, or side effects such as whether files are moved to trash or permanently removed.

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 sentences, front-loaded with the core action. Every word earns its place, and the default behavior is highlighted effectively.

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?

The tool is simple, but without annotations or an output schema, the description should clarify side effects (e.g., permanent deletion) and success/failure behavior. The current description covers basic functionality but leaves out important operational details for a destructive operation.

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 100%, with parameters well-documented in the schema. The description adds a brief paraphrase of filters but does not add significant semantics beyond the schema.

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 action ('Delete screenshots') and resource (screenshots). It distinguishes from siblings like delete_image by indicating bulk deletion with filters, while delete_image likely handles individual images.

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 gives context on when to use: default deletes all, with options to filter by age or filename pattern. It does not explicitly compare to alternatives like delete_image, but the behavior is clear enough for an agent to infer bulk cleanup use.

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