copy_file

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

The description does not disclose any behavioral traits beyond the basic copy operation. No annotations are provided, so the description carries the full burden. It fails to mention whether the destination file is overwritten, permissions required, error handling, or any side effects. This is insufficient for an agent to understand the tool's full impact.

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 very concise, with a clear first sentence stating the purpose, followed by a usage line and parameter details. There is no unnecessary verbosity. However, the omission of 'agent_id' detracts from its efficiency, as it could have been included in the parameter list succinctly.

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 with 3 required parameters and no annotations, the description is incomplete. It lacks details about return values (despite having an output schema), agent_id parameter, and behavioral traits like overwrite behavior. The context signals indicate low coverage, and the description fails to compensate adequately.

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 description adds meaning for 'src' and 'dst' parameters with types and examples, and suggests an order via 'cp <src> <dst>'. However, it completely omits the required 'agent_id' parameter, which is not described or mentioned. Given schema description coverage is 0%, the description should compensate but fails to address all parameters.

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 on the agent' which clearly conveys the primary action and resource. The usage and example further clarify the intent. However, it does not explicitly differentiate from the sibling tool 'move_file' by stating that the source is not deleted after copying, which would be a minor improvement.

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 provides a usage format and example but offers no guidance on when to use this tool over alternatives like 'move_file' or 'remove_file'. There is no mention of prerequisites, best practices, or scenarios where this tool is preferred, which is a significant gap.

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