drive_files_create

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

With no annotations, the description should disclose behavioral traits. It mentions optional file upload but does not specify required permissions, idempotency, or side effects beyond creation. The term 'bodyParams' is ambiguous and not present in the schema.

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 two sentences, no redundancies. However, 'Use with bodyParams' is unnecessary jargon that could confuse agents.

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 5 parameters and no output schema, the description should provide more context on usage, return values, and prerequisites. It only covers the basic creation action and optional upload, missing key details like required permissions or folder placement.

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 baseline is 3. The description adds minimal value by mentioning optional file upload corresponding to 'uploadPath'. However, 'bodyParams' is misleading as it is not a parameter, reducing clarity.

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 tool creates a new file in Google Drive, specifying the resource and action. It distinguishes from siblings like 'drive_files_copy' and 'drive_files_update' by focusing on creation, but does not explicitly differentiate from them.

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 provides no guidance on when to use this tool versus alternatives (e.g., 'drive_files_copy' for copying, 'sheets_values_append' for appending to sheets). It lacks exclusion criteria or usage context.

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