create-upload-session

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds that the tool returns a pre-authenticated uploadUrl for further PUT requests, which is useful context. It does not mention any side effects or required permissions, but annotations already signal mutability. No contradiction with 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 two sentences plus a tip, making it relatively concise. The first sentence ('Invoke action createUploadSession') is redundant with the tool name and could be omitted, but the rest is well-structured and front-loaded with key information.

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 has 5 parameters, nested objects, and no output schema, the description provides essential information: it returns an uploadUrl for direct PUT. However, it lacks details about the required path parameters (driveId, driveItemId), the response structure, and error handling. The example body is useful but not comprehensive.

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 80%. The description includes an example for the 'body' parameter showing conflictBehavior, which adds value beyond the schema. However, it does not explain the 'driveId' or 'driveItemId' path parameters, and the optional 'includeHeaders' and 'excludeResponse' are not mentioned. The example is helpful but incomplete.

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 is for creating upload sessions for large files and specifies it returns a pre-authenticated upload URL. The tip distinguishes it from standard uploads by noting 'no size limit', but does not explicitly contrast with sibling tools like 'upload-file-content' or 'create-mail-attachment-upload-session'.

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 context for when to use it (large file uploads) and mentions the returned uploadUrl for direct PUT. However, it does not specify when not to use it or suggest alternative tools for smaller files or different scenarios.

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