Move or Copy Files

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

Annotations already mark destructiveHint=true, and the description adds useful context about path interpretation ('full new path, not a folder') and automatic parent directory creation. However, it does not disclose whether move mode overwrites existing destinations by default, a critical behavioral detail given the destructive hint and the copy-only scope of the overwrite parameter.

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 two sentences with no redundancy. It front-loads the primary purpose, then immediately adds a key behavioral caveat. Every phrase earns its place.

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 description covers purpose, path semantics, and parent creation, which are essential. However, it leaves overwrite behavior in move mode ambiguous—whether move overwrites without confirmation—especially since the schema states overwrite applies only to copy mode. This is a significant gap for a destructive tool and reduces completeness.

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 coverage is 100%, so parameters are fully documented in the schema. The description adds minor clarification for the destination parameter (full path semantics) but does not add value beyond the schema for copy or overwrite, which are already described in their property descriptions.

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's function: 'Move, rename, or copy files and directories, like mv or cp -r.' It names specific operations and the resource type, distinguishing it from siblings like create, delete, or edit. The additional note about destination being a full path further clarifies scope.

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 implies usage for moving, renaming, or copying but does not explicitly state when to use this tool over alternatives like create or delete. It lacks exclusions or conditions that would help an agent choose between tools, leaving the decision to inference.

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