direct_upload_advideo

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

Without annotations, the description carries the full burden. It discloses the write nature, return value, and suggests asynchronous polling, but omits details on permissions, file requirements, or potential errors.

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 a single sentence, densely packed with key information without redundant words.

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?

Despite the terse clarity, the description leaves out essential details about the required 'name' parameter and the 'dry_run' flag. Given no output schema and low schema coverage, this is a notable gap for an upload tool.

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 only 20% (only allow_write has a schema description). The description clarifies that file_path and video_base64 are alternative inputs and that allow_write must be true, but it fails to explain the required 'name' parameter or the 'dry_run' parameter.

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 opens with 'WRITE: advideos.add' which clearly identifies a write operation to add a video. It specifies the input methods (file_path or base64), distinguishing it from sibling tools like direct_upload_adimage.

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?

It instructs to poll status with list_advideos, providing a clear post-usage step, and requires allow_write=true. However, it doesn't explicitly contrast with alternatives or state when not to use.

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