copy-asset

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

With no annotations provided, the description fully covers behavioral traits: it's a write operation via WebDAV, requires authentication, refuses certain paths, and explains that references are unaffected. This is comprehensive for a tool lacking annotations.

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 three sentences, each providing essential information without waste. The first sentence specifies the primary action and channel, followed by important clarifications. Ideal conciseness.

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 tool's complexity (3 parameters, no output schema), the description covers all necessary context: the exact operation, constraints (no reference check, path restrictions), and requirements (password). No gaps.

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%, so baseline is 3. The description does not add additional meaning beyond the schema for the parameters; it merely restates the context. No deduction or bonus needed.

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 'Copy a file under the Foundry `Data/` root over WebDAV', using a specific verb and resource. It clearly distinguishes from sibling tools like move-asset, upload-asset, and download-asset.

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?

Explicitly states when not to use (refuses live world-DB destination paths) and a requirement (MOLTEN_WEBDAV_PASSWORD). Also explains that copying doesn't affect references, guiding the agent to use this instead of move-asset when preservation of references is desired.

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