copy_item

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

With no annotations, the description must disclose behavioral traits, but it only says 'Copy a file or folder' and 'account token only'. It does not mention whether directories are copied recursively, what happens on destination conflicts, whether the source is preserved, or what authentication is required beyond the terse token hint.

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, front-loaded sentence with no filler words. However, for an 8-parameter operation with cross-repo and multi-token implications, this level of brevity is under-specification rather than appropriately concise structure.

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 8 parameters, no annotations, no output schema, and no parameter descriptions, the description is far too incomplete. An agent cannot correctly determine how to specify destination repositories, whether tokens are mutually exclusive, or what result to expect, so the tool is underspecified to the point of being unsafe to invoke.

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 description adds minimal meaning over the schema: 'file or folder' loosely suggests is_dir, and 'Copy' implies path and dst_dir roles, while 'account token only' points to account_token. However, the other six parameters (repo_id, dst_repo_id, library_name, session_token, etc.) are left entirely unexplained, and schema coverage is 0%.

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 operation: 'Copy a file or folder'. This provides a specific verb and resource that distinguishes it from related tools like rename_item and move_item, though it does not explicitly name those siblings or describe its exact scope boundaries.

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?

There is no guidance on when to use copy_item versus alternatives such as move_item or upload_file. The parenthetical 'account token only' hints at an auth requirement but does not explain when copying is appropriate or what conditions would make a different tool preferable.

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