drive_files_copy

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

No annotations; description adds minimal behavioral info (conversion) but omits details on permissions, overwriting, or response format.

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 concise sentences, front-loaded with core purpose, no filler.

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?

Minimal coverage given 5 parameters and no output schema; lacks explanation of return values, prerequisites, or behavior of optional parameters like fields and parents.

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?

All parameters documented in schema; description adds context for mimeType parameter regarding format conversion, but no further value for other 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?

Clearly states 'Copy a file' and highlights format conversion, distinguishing it from other drive tools like create, download, or export.

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 use case for conversion but does not provide when-not-to-use or compare with siblings like drive_files_export or drive_files_create.

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