create-upload-session

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

Annotations already mark destructiveHint=true. The description adds that the tool returns an uploadUrl for direct PUT of bytes, which is essential behavioral info. It does not contradict annotations and provides useful context beyond what annotations offer.

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 brief and front-loaded with the action name. It includes a tip, path example, and optional body in a compact form. Some formatting (e.g., separating the tip) could improve readability, but overall 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?

The description covers the main purpose and basic usage, but lacks details on how to use the returned uploadUrl (e.g., time limits, completing the upload) and the full response structure. Since there is no output schema, more return value detail would be beneficial.

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 83% with good parameter descriptions. The description gives a path example using parentId/filename, but the schema expects driveId and driveItemId, which may confuse. The description adds minimal value beyond schema for parameters, so baseline 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 the tool invokes createUploadSession for large file uploads and returns a pre-authenticated uploadUrl. It differentiates itself from siblings like upload-file-content by specifying 'large file uploads (no size limit)', but could be more explicit about when to use this over direct upload.

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 provides usage context: use for large file uploads with no size limit, and gives a path example for new files. However, it does not explicitly exclude small files or name alternative tools like upload-file-content.

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