move_file

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's mention of moving/renaming is consistent. It adds value by explaining path normalization and the constraint of allowed directories. Lacks details on conflict behavior or atomicity.

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 well-structured with a clear action statement, followed by capabilities and constraints. The 'IMPORTANT' section is front-loaded but could be slightly more concise. No redundant phrases.

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?

Covers main usage aspects: allowed directories, absolute paths, normalization. However, lacks details on return values, error handling, or behavior when destination exists. For a move/rename tool, this is adequate but not fully comprehensive.

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?

With 0% schema description coverage, the description compensates by explaining that both parameters are paths, must be absolute, and within allowed directories. Provides essential context beyond the schema's type-only definition.

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 states the tool moves or renames files and directories, specifying both source and destination must be within allowed directories. It distinguishes itself from other file tools like create_directory or write_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?

Provides explicit guidance on using absolute paths, explains why relative paths may fail, and warns about tilde paths. Also mentions how to reference the tool. Does not explicitly contrast with alternative tools but provides clear contextual usage.

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