assets-copy

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

The description discloses that AssetDatabase.Refresh() is called, a useful side effect, but does not mention overwrite behavior, error handling, or whether the operation is atomic, which is needed since no annotations are provided.

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 two sentences, front-loads the main action, and includes a key usage tip without extraneous information.

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?

No output schema is present, and the description does not explain return values or error states. It covers the main action and a side effect, but lacks details on handling multiple paths or failure modes.

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 input schema has 100% coverage with clear parameter descriptions. The description adds an example and a hint about using assets-find, but does not significantly enhance understanding beyond the schema.

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 copies an asset from one path to another, distinguishing it from siblings like assets-move or assets-delete. However, it uses singular 'path' while the schema accepts arrays, causing slight ambiguity.

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 advises using 'assets-find' before copying, which is helpful context, but it does not specify when to avoid copying or when to use alternatives like assets-move, leaving room for improvement.

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