copy_move_item

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

Discloses the move/overwrite behavior and default values, but does not specify error handling (e.g., if destination missing, if overwrite=false and file exists) or side effects (e.g., recursive move for folders). No annotations provided, so description carries full burden but falls short.

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?

Description is short and front-loaded with the main purpose, then bulleted args. No fluff, but the unexplained '[control]' tag adds minor confusion. Overall efficient.

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?

Despite having an output schema, the description omits critical details like error scenarios, behavior for multiple paths, and folder traversal rules. For a 4-parameter tool, this is insufficient for complete understanding.

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 coverage, the description fully compensates by explaining each parameter: paths as comma-separated, dest_folder as existing folder, move as boolean toggle, overwrite as existing file handling. Adds meaning beyond the schema's titles and defaults.

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 'Copy or move files/folders into an existing destination folder,' specifying the verb (copy/move), resource (files/folders), and context (existing destination). This distinguishes it from siblings like delete_item or rename_item.

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 this tool versus alternatives (e.g., create_folder, rename_item). No mention of prerequisites like source existence or destination validity, leaving the agent to infer usage context.

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