Copyfile

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

With no annotations, the description carries the full behavioral burden, and it does disclose one meaningful trait: paths are confined to the configured current directory (a sandbox boundary not visible in the schema). It omits other key mutation behaviors, such as whether an existing destination is overwritten, whether directories are created, or how permission failures surface.

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?

A single, front-loaded sentence with no wasted words. It is efficient, though its brevity is closer to under-specification than true economy.

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 mutation tool with no annotations and zero parameter documentation, the description is too thin: it says nothing about overwrite semantics, error conditions, or the source/destination roles. An output schema exists so return values need not be explained, but the input-side gaps remain significant.

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 0%, so the two parameters (source, destination) are undocumented in both schema and description. The phrase 'beneath the configured current directory' hints that both are paths relative to that root, but nothing states which is read, which is written, or whether traversal is allowed.

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 names a specific verb (copy) and resource (a local file), and adds a real scope constraint: the file must live beneath the configured current directory. It does not, however, differentiate itself from close siblings such as moveRenameFile or writeFile, which is what would push this to a 5.

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 copyFile versus moveRenameFile (move semantics) or writeFile (create/overwrite content). The agent must infer usage purely from the verb, with no stated prerequisites or exclusions.

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