Copy

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

Annotations already indicate this is not read-only, so the description adds little about mutating behavior. It does not disclose what happens on conflicts, whether intermediate folders are created, how autorename interacts, or whether the source is preserved. No contradiction with annotations exists.

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, direct sentence with no filler or redundant elaboration. It is front-loaded and every word contributes to the basic purpose.

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 mutating tool with no output schema and an open-world annotation, the description is too sparse. It omits important context about conflict behavior, autorename semantics, and what the operation returns or changes, leaving the agent to guess about critical execution details.

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 no parameter-level meaning beyond the input schema. With schema description coverage at only 33%, the description should compensate for undocumented parameters like autorename, but it does not mention any parameters at all.

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 states a specific verb ('Copy') and resource ('a file or folder') with a clear destination ('a new path'). It is unambiguous about what the tool does, though it does not explicitly distinguish itself from the sibling dropbox_move beyond the verb itself.

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 implies when to use the tool: when a file or folder should be copied to a new path. However, it gives no explicit guidance about when not to use it or when dropbox_move or other alternatives would be more appropriate.

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