Move or Copy Files

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

Given destructiveHint is already true, the description adds substantial behavioral context: parent directories are created automatically, existing destinations trigger a confirmation that causes the call to return without moving anything, overwrite bypass exists only in copy mode, and self-moves are silently skipped. This goes well beyond the annotations.

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 dense but every sentence earns its place. It front-loads purpose, then gives the input form, then explains edge-case behaviors. No filler or repetition of schema details.

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?

The description covers the operation limit, required array form, destination handling, parent directory creation, copy semantics, overwrite confirmation, and self-move behavior. For a tool without an output schema, this provides ample context for correct invocation.

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 coverage is 100%, so the schema already documents all parameters. The description adds meaning beyond the schema by clarifying the exact call shape ('Pass moves: [{ source, destination }]') and emphasizing that there is no single-pair form, plus the effect of copy and overwrite on runtime behavior.

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 begins with a specific verb and resource: 'Move, rename, or copy files and directories to explicit destination paths.' This clearly distinguishes the tool from siblings like create, delete, and edit, while also noting the 100-operation limit.

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 gives clear context for use: pass an array of move pairs, there is no single-pair form, and copy=true switches to copy mode. It does not explicitly state when not to use this tool versus siblings like edit or delete, but the intended use is strongly implied by the tool's purpose.

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