drive_files_copy

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

Beyond the annotation indicating a write operation, the description does not disclose behavioral details such as permissions needed, whether the original is preserved, or what happens during conversion. No contradictions with annotations.

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?

Extremely concise: two sentences with no unnecessary words. The key action and a practical use case are front-loaded.

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?

Despite only 5 parameters and no output schema, the description lacks context about the copy behavior (e.g., permissions, location), the parents parameter, and the fields parameter. It leaves significant gaps for an agent to infer.

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?

With 100% schema coverage, the baseline is 3. The description adds minimal value by hinting at the mimeType parameter with an example, but does not elaborate on 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?

The description clearly states the verb 'copy' and resource 'file', and provides a specific use case (format conversion). This distinguishes it from siblings like drive_files_create and drive_files_update.

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?

It implies usage for copying and converting formats but lacks explicit guidance on when to use this tool vs alternatives like drive_files_export or drive_files_create. No when-not-to conditions are mentioned.

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