Upload Capacities media files

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

Though annotations already indicate a mutating, open-world, non-idempotent operation, the description adds significant behavioral detail: 'Streams multipart files without loading them into the model or memory, verifies each completed object with GET, and returns partial results when independent files fail.' This transparency goes well beyond the structured 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 three sentences: purpose, key behavioral traits, and usage guidance. It is front-loaded and concise, with every sentence contributing meaningful information and no redundancy.

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's complexity, the description covers streaming, verification, partial failures, and background processing, and it points to manage_upload_job for lifecycle control. With an output schema present, there is no need to explain return values, making this contextually complete.

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 schema already provides 100% parameter descriptions, including mode options, file path rules, and API token behavior. The description only references mode=background without adding new parameter-level semantics, so the default baseline of 3 applies.

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 verb and resource: 'Upload one or more local files to Capacities as media objects.' It distinguishes from siblings by explicitly focusing on local file uploads and media objects, and it references manage_upload_job for background job handling, making the tool's role clear.

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 explicit guidance for when to use background mode: 'Use mode=background for long or large batches, then manage_upload_job for status, wait, or cancel.' It names a complementary tool but does not explicitly state when not to use upload_files versus other content creation tools, so it falls slightly short of full exclusion guidance.

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