drive_upload_file

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

With no annotations provided, the description carries the full burden. It discloses behavioral details such as the server reading the file from disk and isBase64 applying only to content. However, it omits potential mutation consequences (e.g., overwrite behavior), authentication needs, and error handling, leaving gaps for a write operation.

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 two sentences, front-loaded with the core action, and contains no redundant information. Every phrase contributes essential usage instructions, making it highly concise and well-structured.

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 7 parameters and no output schema, the description adequately covers input modes but does not explain what the tool returns (e.g., file ID) or error/conflict outcomes. This leaves the context somewhat incomplete for a tool of this complexity.

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% with individual parameter descriptions. The description adds meaningful value by clarifying the relationship between content, filePath, and isBase64, and noting that the server reads the file directly. This supplements the schema beyond what the property descriptions provide.

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 explicitly states 'Upload a file to Google Drive' with a clear verb and resource. It also distinguishes from sibling tools by detailing content delivery methods (UTF-8 text, base64, file path), making the purpose unambiguous.

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 clear usage context by explaining how to provide content (text, base64, or file path) and when to use isBase64. It implies use for uploading files to Drive but does not explicitly mention when not to use it or reference alternatives, which is acceptable for a direct upload tool.

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