move_file

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

With no annotations, the description carries the full burden. It adds the constraint 'within allowed directories' but fails to disclose important behaviors such as overwrite semantics, cross-filesystem support, permission requirements, or success/error return behavior. This is minimal 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?

The description is a single, clear sentence with no filler. It delivers the core purpose and a key constraint efficiently.

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 absence of annotations and output schema, the description should explain more about behavior, return values, and edge cases. It only states the move capability and the directories restriction, leaving unclear what happens on success or failure, and whether any side effects (e.g., overwriting) occur.

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%—both parameters have descriptions in the input schema. The tool description does not add parameter-specific information beyond the schema, so the baseline of 3 applies. The 'allowed directories' hint indirectly affects possible values but is not parameter-specific.

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 identifies the action 'Moves' and the target 'a file or directory to a new location,' distinguishing it from siblings like copy_file (copy) and delete_file (remove). The scope 'within allowed directories' adds specificity.

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 implies usage for relocating files/directories but does not explicitly state when to choose this over copy_file or delete_file, nor does it mention exclusions/alternatives. The context is clear but not explicitly differentiated.

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