Copy any file in Google Drive to a new location with optional rename and parent folder assignment.
Copy a file in Google Drive
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Name for the copied file | |
| fileId | Yes | The ID of the file to copy | |
| parentId | No | Parent folder ID for the copy |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only says 'Copy a file', failing to disclose behavioral traits such as permission handling, idempotency, or error states. The description does not add value beyond the basic action.
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 sentence, which is too brief. It lacks any structure or detail, and the brevity leads to under-specification rather than 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 no output schema and only 3 parameters, the description should at least mention return value (e.g., copied file ID) or error conditions. It provides none, making it incomplete for a file copy operation.
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 all three parameters (name, fileId, parentId) are documented in the input schema. The description adds no extra meaning, so baseline 3 is appropriate.
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?
Description clearly states 'Copy a file in Google Drive', which is a specific verb+resource. However, it does not differentiate from sibling tools like drive_create_file or drive_move, missing an opportunity to clarify scope.
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 on when to use this tool versus alternatives like drive_create_file or drive_move. No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.