Create Resumable Upload Session

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

The description adds key behavioral context not covered by annotations: it explains that the caller will PUT bytes directly to Google, bypassing MCP transport limits, and that only the URL travels through MCP. This goes beyond the readOnlyHint and openWorldHint 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 description is very concise, with five sentences that are front-loaded with the main purpose. Every sentence adds value, and there is no unnecessary elaboration.

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 complexity, the presence of an output schema, and 80% schema coverage, the description provides sufficient context for an agent to understand the tool's role. It explains why the session is resumable and how it bypasses limits. However, it could mention session expiry or that the URL is temporary for full completeness.

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 80%, so the schema already documents most parameters well. The description adds no extra parameter-specific meaning beyond what is in the schema, just mentions the return of upload_url. Baseline score of 3 is appropriate.

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 it creates a Google Drive resumable upload session and returns the upload URL, specifying the verb and resource. However, it does not explicitly distinguish itself from the sibling 'create_file' tool, so while clear, it misses some differentiation.

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?

No explicit guidance on when to use this tool versus alternatives like 'create_file'. The description implies it is for large files bypassing MCP limits, but this is not stated as a usage rule or contrasted with other tools.

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