Move File

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

Beyond the destructiveHint annotation, the description adds key behavioral details: the operation fails if destination exists, and both paths must be within allowed directories. However, it does not explicitly confirm that the source is removed after the operation.

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 front-loaded with the core action in the first sentence. It is slightly wordy with five sentences, but each adds value. Could be tightened by combining sentences without losing meaning.

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 moderate complexity, the description covers the main behaviors (move/rename, failure condition, allowed directories). An output schema exists, so return value details are not needed. However, it omits stating explicitly that the source is deleted, which is a minor gap.

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?

The input schema provides no descriptions for source or destination (0% coverage), so the description must compensate. It only adds a constraint (must be within allowed directories) but does not explain path format, relative vs absolute, or that source is the original location and destination is the new location.

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 uses specific verbs 'move or rename' and clearly identifies the resource (files and directories). It distinguishes itself from sibling tools like copy or delete by stating it moves/renames, and mentions it can work within or across directories.

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 (moving/renaming) but does not explicitly state when to use this tool versus alternatives like copy or delete. It notes a failure condition but lacks guidance on when not to use it or prerequisites.

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