create-upload-session

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

The description reveals that the tool creates an upload session and returns a pre-authenticated upload URL, beyond the annotations' destructiveHint. It does not discuss rate limits, authorization, or session expiration. Annotations already indicate mutation, so description adds moderate context.

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 three sentences, front-loading the action name and key benefit. No superfluous 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 complexity (5 parameters, nested objects, no output schema), the description explains the return value but lacks details on error handling, parameter options, and prerequisites. It does not fully cover the tool's 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?

The description briefly mentions the body parameter for conflict behavior but does not describe driveId, driveItemId, includeHeaders, or excludeResponse. With 80% schema coverage, the description adds minimal value beyond the schema's parameter descriptions.

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 large file uploads with no size limit and returns an upload URL. It distinguishes from other upload tools by emphasizing the session approach and large file capability. However, the initial sentence 'Invoke action createUploadSession' is somewhat tautological, though the following sentences clarify.

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 this tool (large files) and includes a tip for new files with conflict behavior. However, it does not explicitly contrast with siblings like upload-file-content or create-mail-attachment-upload-session, nor does it state when not to use it.

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