Copy Drive File

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

Annotations indicate readOnlyHint=false, confirming a write operation, but the description adds useful context: 'The copy maintains all formatting and content from the original file.' This goes beyond the annotations and explains a key behavioral trait. No contradictions with annotations are present.

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 concise, with three sentences that each add value: purpose, copying behavior, and preservation of formatting. It is front-loaded and avoids redundancy or fluff.

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 core behavior and mentions key options (new name, destination). An output schema exists (as indicated in context signals), so return value details are not required. It doesn't address permission inheritance or auth flow, but given the annotations and schema, the description is sufficiently complete for a 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 the parameters are well-documented in the schema itself. The description mentions 'template document' and 'new location,' which loosely align with file_id and parent_folder_id, but it does not add significant semantic meaning beyond the schema's parameter descriptions.

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 'Creates a copy of an existing Google Drive file' with a specific verb and resource, distinguishing it from sibling tools like create_file or update_drive_file. It also specifies that the copy goes 'to a new location with an optional new name,' which further clarifies its unique function.

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 implies the tool is for copying existing Drive files, with mention of 'template document' as a common use case. While it doesn't explicitly name alternative tools or state when not to use it, the context is clear enough for an agent to infer appropriate usage.

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