drive_upload

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

With no annotations, the description carries the full burden and does well: it discloses the copy-to-phone, system-picker, upload, and delete-phone-copy lifecycle, plus the blocking semantics (waits until the item appears and the progress bar settles). It omits name-collision/overwrite behavior and permission or size constraints, which matter 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?

Three sentences, front-loaded with the action and the resource, with the parenthetical UI path and the wait condition each earning their place. The mechanism sentence is slightly long but conveys information the agent cannot get from the schema.

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?

For a mutation tool with no annotations, no output schema, and four fully-documented parameters, the description covers the important gap: that this is a blocking, multi-step operation with a temp-file side effect. Missing pieces are conflict handling when a file of the same title exists and what happens on timeout.

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 all four parameters (including defaults for path and title) are already documented, which sets the baseline at 3. The description adds only a light chaining hint that the file lands "under title into the folder"; it adds nothing about local_path vs. the transient phone copy or about the timeout parameter.

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?

States a specific verb and resource ("Upload a file from this computer into a Drive folder") and even names the UI affordance it mirrors ("Create new > Upload"). It does not, however, distinguish itself from the very similar siblings drive_upload_files and drive_upload_folder, which is a real ambiguity given three near-identical names.

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?

Usage is implied by the phrasing "Upload a file from this computer" — i.e., use this when the source is a local path rather than an existing Drive item. There is no explicit when-not guidance or pointer to drive_upload_files/drive_upload_folder for multi-file or folder cases, leaving the agent to infer the boundary.

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