fs_move_directory

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

No annotations are provided, so description must disclose behavior. It does reveal a key failure condition ('fail if destination exists') but omits interaction with the 'overwrite' parameter, permission requirements, and move semantics (e.g., atomicity, parent dir creation). This leaves important behavioral gaps for a mutating 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?

Single concise sentence, front-loaded with verb and resource, zero filler. It states the core operation and one critical constraint in minimal words.

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?

Despite having an output schema, the description is too sparse for a mutation tool. Overwrite semantics, error behavior beyond existence check, and any required preconditions are absent. The two required path parameters and optional overwrite need more explanation for safe use.

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% and the description provides no parameter semantics. The overwrite parameter is entirely unexplained, and source_dir/dest_dir formats or constraints are not described. Description fails to compensate for the schema's lack of documentation.

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 a specific verb 'move' and resource 'directory', clearly distinguishing it from sibling fs_move_file. The fail-if-exists condition adds behavioral specificity beyond a generic move.

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?

No explicit guidance on when to use vs alternatives like fs_copy_directory or fs_move_file. The context implies usage for moving directories, but the tool doesn't state when to choose it over siblings or when not to use it.

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