assets_copy

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and destination; it does not mention overwrite behavior, whether the source must already exist in the store, authentication requirements, or the operation's result/return value. This is a significant gap for an operation that could mutate or fail in various ways.

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 sentence with no redundant details. The verb and core object are front-loaded, and every word contributes to the essential purpose. It is appropriately concise.

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 the absence of annotations and output schema, the description does not cover return values, failure conditions, or edge cases like overwriting existing paths. It is adequate for understanding the basic action but lacks behavioral context needed for reliable 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 description coverage is 100%: both `fromUrl` and `toPathname` have descriptive text. The description adds minimal additional meaning beyond mentioning 'new path', which maps to `toPathname`. Baseline of 3 applies because the schema already documents parameters adequately.

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 uses the specific verb 'Copy' with a clear resource ('an asset') and destination ('a new path in your personal assets store'). It is discernibly different from siblings like upload/delete, though it does not explicitly name an alternative to distinguish 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?

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'Copy an asset to a new path' implies a duplication scenario, but the description does not state exclusions, prerequisites, or comparative conditions against upload/delete.

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