move_file

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

Annotations already declare destructiveHint=true, signaling potential deletion or modification. The description adds context about path normalization and allowed directories but does not disclose behavior if destination already exists (e.g., overwrite or error). This is a notable gap for a destructive 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 concise with two short paragraphs. The first sentence immediately states the core purpose. The second paragraph contains essential usage notes. No unnecessary information, and structure is front-loaded effectively.

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 simple two-parameter schema and lack of output schema, the description covers purpose, constraints, and path guidance. It lacks details about return values, error conditions, or behavior on conflict, but overall it provides sufficient context for basic usage.

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 has 0% description coverage for both parameters. The description clarifies that source and destination are paths and recommends absolute paths, adding some guidance. However, it does not explicitly describe each parameter's expected format (e.g., source must be an existing file/directory) or constraints beyond paths.

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 explicitly states the tool moves or renames files and directories, using specific verbs and resources. It clearly distinguishes from sibling tools like write_file or create_directory by focusing on relocation/renaming rather than creation or content modification.

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 provides explicit guidance on using absolute paths, warnings about relative and tilde paths, and mentions that source and destination must be within allowed directories. However, it lacks explicit 'when not to use' or comparison to alternatives like copy instead of move.

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