move_file

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention what happens to the source file after moving, how the overwrite parameter affects behavior, whether the operation is atomic, or what errors can occur. The only clue is the word 'move,' which implies source removal but lacks detail.

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, concise sentence: 'Move file from source to destination.' It is front-loaded with the action and resource, contains no extraneous words, and fully earns its place.

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 move operation with two required parameters and an optional overwrite flag, the description is minimally adequate, but it lacks crucial behavioral context such as overwrite implications and error handling. The presence of sibling tools like copy_file highlights the need for clearer differentiation, but the description itself does not address that. Overall, it is usable but incomplete for an AI agent.

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?

The schema already provides full descriptions for all three parameters (source, destination, overwrite), giving 100% schema coverage. The description adds no new semantic details about parameters, so it neither enhances nor detracts from the schema; the baseline 3 applies.

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 'Move file from source to destination' uses a specific verb and resource, clearly distinguishing the operation from siblings like copy_file or delete_file. The action is unambiguous and directly tied to the tool's functionality.

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 no guidance on when to use this tool versus alternatives such as copy_file or write_file. It does not mention any prerequisites, exclusions, or context-specific recommendations, leaving the agent to infer usage from the tool name alone.

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