Move File

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

Annotations already declare destructiveHint: true, indicating the tool modifies the filesystem. The description adds transparency by stating the operation will fail if the destination exists, and that both source and destination must be within allowed directories. However, it doesn't clarify whether renaming is destructive (replaces existing data at source after move), though annotations partially cover this.

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 three sentences, each adding distinct value: first states overall function, second explains failure behavior, third clarifies scope. It is front-loaded with the key purpose. Could be slightly more concise (e.g., 'rename' is repeated) but is efficient overall.

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 has 2 parameters, an output schema exists (handling return values), and annotations already provide behavioral hints, the description is reasonably complete. It covers the key constraint (destination must not exist) and the allowed directory scope. One minor gap: it doesn't specify that the tool can also rename in-place (implied but not explicit).

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 description coverage is 0%, meaning the schema provides no descriptions for the two parameters. The description fully compensates by explaining that source is the path to the file or directory to move/rename, and destination is the new path. The description adds meaning about cross-directory moves and same-directory renaming, which is essential since the schema lacks any parameter 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 it moves or renames files and directories, specifies that it can both move between directories and rename in one operation, and notes that the operation will fail if the destination exists. This distinguishes it from sibling tools like filesystem__write_file or filesystem__create_directory, which do different operations.

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 explains when to use this tool (moving/renaming files or directories, including across directories), but does not explicitly mention when NOT to use it or provide alternatives. However, the context of sibling tools (e.g., filesystem__write_file, filesystem__create_directory) provides implicit guidance.

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