copy

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

No annotations exist, so the description carries the full burden. It discloses overwrite behavior and provides example paths, but does not explain recursive folder copying, error handling, permissions, or return values. For a mutation operation, this is a moderate level of disclosure.

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 clear headline followed by a structured argument list. Every sentence serves a purpose—stating the action, defining parameters, and clarifying overwrite semantics—with no filler or redundancy.

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?

The description covers the action and parameters well for a standard copy operation, but lacks an output/return value description. Given the absence of an output schema and annotations, a brief note on success indication or error behavior would make it fully complete. The provided examples and overwrite detail raise it above a bare minimum.

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 no parameter descriptions (0% coverage), but the tool description fully compensates by explaining src, dst, and overwrite with examples and a default behavior. This is the strongest possible compensation for missing schema metadata.

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 or folder to a new location' with a clear verb and resource, and the parameter list confirms specific behavior. This differentiates it from sibling tools like move and rename by explicitly indicating duplication rather than relocation.

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 does not explicitly state when to use copy versus alternatives (move, rename). Usage is implied by the verb and semantics, but no exclusionary or comparative guidance is provided.

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