move_file

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

The description adds a critical behavioral constraint—the require allow_file_write permission—beyond the annotations, which provide no safety hints. It does not detail overwrite behavior or failure modes, but the permission requirement is valuable context.

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, front-loads the core action, and adds only essential use cases and permissions. No redundant information.

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?

For a simple two-parameter file operation, the description covers purpose, when to use, and a key prerequisite. It does not mention return values or overwrite behavior, but the tool is simple enough that this is acceptable.

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 100%, with both src and dst already documented in the schema. The description does not add further parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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/directories, and lists concrete use cases (renaming, moving, reorganizing). This clearly distinguishes it from sibling tools like copy_file or delete_file.

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?

It clearly states when to use the tool ('Use for renaming files, moving files to different folders, or reorganising directories'). It does not explicitly exclude alternatives like copy_file, but the scope is clear enough.

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