Copy Drive File

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

Adds that the copy maintains formatting and content, which is useful. Annotations already indicate it is not read-only and not destructive, so the description provides minor additional behavioral context but no details on permissions, rate limits, or side effects.

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?

Two sentences, front-loaded with the core purpose, second sentence adds key detail. No extraneous words.

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 simple copy tool with 100% schema coverage and an output schema, the description covers the main behavior. Lacks mention of required permissions (e.g., user must have access to source and destination), but overall sufficient given annotations.

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 coverage is 100%, so the description adds little beyond the parameter descriptions. The mention of 'optional new name' is already in the schema. No additional parameter-level information beyond schema.

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?

Clearly states it creates a copy of an existing Google Drive file, with specific verb 'copies' and resource 'existing Google Drive file'. Differentiates from sibling tools like create_drive_file (creates new) and update_drive_file (modifies existing) by focusing on duplication.

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?

Implies usage for copying existing files but does not explicitly state when to use this tool versus alternatives like create_drive_file or update_drive_file. No guidance on prerequisites (e.g., user must have read access to original file and write access to destination).

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