create-upload-session

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

Annotations indicate destructiveness and non-read-only. The description adds context: returns pre-authenticated URL, no size limit, and optional conflict behavior. However, it does not disclose session expiration, one-time use, or other lifecycle details.

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 concise with two sentences and a tip. The code example is helpful but the inconsistency with schema detracts from clarity.

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?

The description covers the main purpose and return value but lacks detail on session behavior, response structure (no output schema), and parameter alignment. The path example mismatches the schema, leaving gaps.

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?

The description adds meaning to the body parameter with an example conflict behavior. However, it introduces a conflicting path format using parentId/fileName instead of driveId/driveItemId. Schema descriptions cover 80% of parameters, but body lacks description.

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 tool creates an upload session for large files and returns a pre-authenticated URL. The tip gives specific usage guidance. However, the example path uses parentId and fileName while the schema requires driveId and driveItemId, causing potential confusion.

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 implies it's for large uploads ('no size limit') but does not explicitly state when to use or avoid this tool, nor does it mention alternatives like upload-file-content. No guidance on when not to use.

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