drive_files_create

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

Annotations already provide the safety profile (readOnlyHint=false, destructiveHint=false). The description adds the nuance that an optional local file upload is supported and that metadata should be supplied via bodyParams, which is useful but limited. It does not disclose side effects, permission requirements, or error/conflict behavior, but with annotations present the bar is lower.

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 short sentences with no filler. The primary action is front-loaded, and each clause adds useful information (creation, metadata via bodyParams, optional upload).

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 the tool has 5 parameters, no output schema, and only these annotations, the description is adequate but minimal. It explains the core purpose and upload option but leaves out potential guidance on parameter combinations, expected response format, or special handling of Google-native MIME types. Still, the schema and annotations carry enough for basic invocation.

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 schema documents all parameters. The description adds limited meaning by mentioning 'bodyParams' and the option to upload a local file, which maps to the uploadPath parameter. This is marginal, so a baseline of 3 is appropriate.

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 action: 'Create a new file in Google Drive' with a specific verb and resource. It is distinguishable from sibling tools like drive_files_copy (copy), drive_files_update (update), and drive_files_delete (delete), and from docs_create/slides_create which create specific doc types.

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 gives a hint about how to call the tool ('Use with bodyParams for metadata and optionally upload a local file') but does not specify when to choose this tool over alternatives like drive_files_copy or docs_create. No exclusions or alternative routing are mentioned, so guidance is only implied.

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