Open upload studio

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

Annotations indicate safe read (readOnlyHint: true) and no destruction. The description adds that it opens a UI, files are staged in Upload-Post/R2 storage and published, and explains why hosted servers cannot access local paths, providing useful behavioral context beyond 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?

Three sentences, each earning its place: first defines purpose, second gives usage guidance, third explains the underlying mechanism. No redundancy or filler.

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?

With no required parameters and an output schema present, the description sufficiently explains what the tool does, when to use it, and how it operates. Complete for an open-UI action.

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 description coverage is 100% and all parameters have descriptions. The description does not add further semantic detail about parameters beyond the schema, 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 it opens a UI for local/attached video uploads, specifying the resource (ChatGPT UI) and action (open). It distinguishes from sibling upload_video by explaining this is for browser-selected files, not server paths.

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?

Explicitly states 'Use this FIRST when the user attaches a video... and does not provide a public HTTPS URL.' and advises against using upload_video first with local paths, giving clear when-to-use and when-not-to-use context.

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