Manage local files and folders

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

Annotations already provide destructiveHint=true, and the description reinforces destructive behavior by mentioning 'delete' and advising verification. It adds context about requiring resolved paths, which is helpful but does not elaborate on idempotency, overwrite behavior, or error handling beyond what annotations imply.

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 purpose. The second sentence is functional but could be clearer. Every sentence earns its place, leaving no unnecessary 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?

Given the tool's complexity (5 parameters, no output schema, destructive operations, multiple siblings), the description is too sparse. It lacks guidance on return values, error states, prerequisites, and how to handle common scenarios (e.g., overwriting, recursive deletion). The agent would need to infer too much from the schema alone.

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 and 5 parameters, the description must compensate but only vaguely alludes to 'targets'. It does not explain source, destination, overwrite, recursive, or their roles. The action enum is partially covered by the list of operations, but the remaining parameters are left undocumented.

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?

Description clearly states the tool performs copy, move, delete, and create operations on local files and folders. The verb+resource combination is specific and distinguishes it from sibling tools like read_file or list_directory, though it does not explicitly contrast with them.

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 instruction 'Use exact resolved targets and verify consequential operations afterward' provides some guidance on safe usage, but it does not specify when to choose this tool over alternatives (e.g., when to use file_operation vs read_file). No explicit when-not or sibling comparisons are given.

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