drive_upload_file

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

Far exceeds the annotations. It discloses the two-phase approval workflow, out-of-band human approval channels behind biometric auth, request expiry (default 15 min), deduplication of identical pending requests, the 20-requests/hour rate cap, audit logging of every phase, and the rationale for approval (files can be shared onward and leave the machine). It also explains that execution uses the approved arguments, not the ones passed the second time — a critical nuance an agent cannot infer from annotations.

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 core action and the two-phase model are front-loaded, and nearly every sentence carries a distinct operational fact (expiry, dedup, rate limit, audit, preview contents, return value). It is dense and fairly long, but the density is justified rather than padding.

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 write tool with no output schema, the description supplies everything needed: the approval lifecycle, the return value ({id, name, link, ...}), security constraints, and the prerequisite of a connected Google account. Nothing required to invoke it correctly is missing.

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 the baseline is 3. The description adds meaning beyond the schema by clarifying that the second call's argument values are ignored in favor of the previously approved payload, which is a semantic subtlety the property description only partly conveys. It also confirms the preview shows local path, resulting name, and destination folder.

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 first sentence states a specific verb and resource: 'Upload a local file to the user's Google Drive.' This cleanly distinguishes it from the drive_* siblings (drive_read_file, drive_list_files, drive_delete_file). An agent immediately knows what this tool does.

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 explicit procedural guidance: call once without request_id to get a preview, obtain out-of-band human approval, then call again with the same request_id to execute. It also states when requests expire and when they are refused (rate_limited), which is strong when-to-use/when-not context. It does not name any alternative tool, but no sibling overlaps this upload use case, so the omission is minor.

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