move

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

No annotations provided, so description carries full burden. States 'Move' but omits critical behavioral traits: whether operation removes source file (implied but not explicit), overwrite behavior if destination exists, atomicity guarantees, or error conditions (e.g., destination folder missing).

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 9-word sentence is appropriately front-loaded with no redundancy, though extreme brevity leaves dangerous gaps for a destructive operation with zero behavioral annotations.

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?

Mutation tool with no annotations and no output schema requires description to disclose side effects (source deletion), conflict resolution, and return values. Current description is inadequate for safe 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 has 100% description coverage ('Current path', 'Destination path'). Description mentions 'new location' which aligns with to_path but adds no syntax details, path format requirements, or examples beyond what schema already provides.

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?

Clear verb ('Move') and resource ('file or folder') with scope ('in Dropbox'), but does not explicitly differentiate from sibling 'copy' or indicate when to prefer copy over 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 guidance on when to use versus alternatives (e.g., 'copy' if source should be preserved), prerequisites, or preconditions like write permissions on destination folder.

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