copy_file

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

With no annotations, the description must disclose behavioral traits but only says it copies files or directories. It misses critical details such as overwrite behavior, recursive copying for directories, permission needs, or side effects, leaving the agent underinformed about the tool's actual behavior.

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 short sentence, making it highly concise and front-loaded with the core action (copy files or directories). It avoids unnecessary words, though it sacrifices informative detail.

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 tool that supports both files and directories with no annotations, the description is incomplete. It fails to address key operational nuances like recursive copy for directories, conflict resolution, or return behavior. The presence of an output schema does not fill the gaps in usage context.

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 schema has 0% description coverage for both required parameters (src_path, dst_path). The description does not explain their meaning, format, or constraints, failing to compensate for the low schema coverage. Parameter names alone are insufficient, as the description adds no semantic value beyond what the schema already implies.

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 that the tool copies files or directories in Nutstore, specifying the verb and resource. It distinguishes from siblings like move_file by implying a copy operation, though it does not explicitly differentiate from alternatives.

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?

No guidance is provided on when to use this tool vs alternatives like move_file, upload_file, or download_file. The description lacks context about appropriate use cases, prerequisites, or exclusions.

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