move_to_trash

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

Beyond the destructiveHint annotation, it discloses that moved items are restorable until Trash is emptied and that certain paths are refused. It also explains the default safe dry-run behavior and what happens when dry_run is false.

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 four sentences with no wasted text, and it front-loads the core action, safety workflow, and dry-run semantics. Each sentence adds useful 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 mutation tool with no output schema and only two parameters, it covers the essential context: safety approval, dry-run behavior, restorability, and refusal cases. 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?

With 0% schema description coverage, the description carries the parameter burden and does well: it explains dry_run's default and effect, and clarifies which paths are refused. The only minor gap is that it does not specify path formatting such as absolute vs relative.

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: move items from the latest scan to the Trash. It also distinguishes the operation from empty_trash by clarifying that items remain restorable until the Trash is emptied.

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 gives an explicit mandatory workflow: show the user the list and total size and obtain explicit approval before acting. It also explains that dry_run defaults to true and must be set to false to perform the move, which clearly defines when and how to invoke the mutation.

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