upload_file

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It states the core action but does not mention whether the file is created new or overwrites existing, required permissions, side effects, or return value. This is a significant transparency gap for a mutation tool.

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 a single concise sentence with no redundant words. It efficiently communicates the essential purpose without fluff, earning its place.

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 four required parameters, no annotations, no output schema, and no parameter descriptions, the description is insufficient for correct invocation. It conveys the overall purpose but leaves the agent to guess parameter roles, behavioral expectations, and return values.

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 0%, so the description must compensate by explaining the parameters. It hints at 'base64-encoded file' and 'Drive folder' but does not explicitly map these to contentBase64, driveId, fileName, or parentId. The parameter names are somewhat self-explanatory, but the description adds minimal semantic value over the bare schema.

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 ('Upload'), the object ('a base64-encoded file'), and the destination ('to a Drive folder'). It distinguishes itself from sibling tools because none of them perform file uploads; it is the only tool with this purpose.

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 or any exclusions. It does not mention prerequisites (e.g., folder existence, permissions), nor does it contrast with related operations like move_drive_item or create_folder.

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