yd_videos_upload

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits such as file size limits, supported formats, overwrite behavior, or whether upload is synchronous. Only mentions base64 encoding but not how it interacts with the file_path parameter.

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?

Single sentence, no filler. Efficiently communicates the primary action.

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?

No annotations or output schema, and the tool is a mutation. Missing contextual details like success/error responses, valid video formats, size limits, and no reference to related tools like yd_videos_get for retrieval. Incomplete for a typical upload operation.

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 covers 100% parameters with descriptions, but the description introduces ambiguity by stating 'base64-encoded' while the schema describes file_path as 'Path to video file on server'. This contradiction leads to confusion about whether the parameter expects a path or the base64 content itself.

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 'Upload' and the resource 'video', with specific context 'from a local file (base64-encoded)'. This distinguishes it from sibling tools like yd_videos_get (get) and yd_ad_images_add (upload image).

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?

No guidance on when to use this tool versus alternatives, no prerequisites or limitations mentioned. The description fails to specify when upload is appropriate or what to do after upload.

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