one_touch_scan

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

Discloses that the tool is non-destructive ('WITHOUT deleting anything') and scans specific types of files. However, no mention of potential performance impact or required permissions, which would improve transparency.

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 concise—two short sentences—front-loading the action and the key constraint of no deletion, with no wasted words.

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 tool with no parameters and no output schema, the description adequately conveys its purpose and usage order relative to siblings. Could mention output format or that results are viewable via other tools, but overall sufficient.

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?

With an empty input schema (0 parameters), the description adds context about the tool's action, but since there are no parameters to explain, the baseline is high and the description provides adequate meaning.

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 scans for junk files and shows what can be cleaned without deleting, and distinguishes it from sibling 'one_touch_clean' by indicating this is a pre-cleaning scan.

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?

Explicitly states 'Always run this first before cleaning,' providing clear when-to-use guidance and implying alternatives like cleaning tools are used subsequently.

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