upload_drive_file_version

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

Discloses key behavioral traits: increments the version counter and makes the uploaded version current. No contradictions with annotations. Could elaborate on the mutation effect (replaces current version), but sufficient for agent understanding.

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 concise sentences: first states purpose and resolution method, second specifies constraints and effect. No redundant phrases; highly efficient.

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 presence of an output schema, the description adequately covers purpose, constraints, and effect. Slightly lacking in error handling or prerequisites, but sufficient for an agent with sibling context.

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?

Adds meaningful context beyond the input schema by emphasizing the mutual exclusivity of source parameters and recommending filePath for large files. Schema coverage is 100%, but the description enriches parameter usage.

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 verb (upload), resource (new version for existing Drive file), and how to resolve the file (by id or path). It effectively distinguishes this tool from siblings like 'upload_drive_file' and 'upload_file'.

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?

Provides explicit guidance on providing exactly one source among filePath, fileUrl, or base64 data, and notes that filePath is preferred for large files. Missing explicit when-not-to-use or alternative recommendations, but the context is clear.

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