Upload YouTube Short

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

The description adds the dry-run behavior beyond what annotations provide (which only indicate mutability). Annotations show readOnlyHint=false and destructiveHint=false, consistent with upload. The vertical video constraint is noted, but missing details like auth requirements or rate limits.

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 two sentences, front-loaded with the core purpose, and contains no filler. Every word is necessary.

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 7 parameters including required fields and enums, and no output schema, the description is too minimal. It does not explain how to specify the video path, title requirements, or effects of optional parameters like privacy_status. The agent lacks sufficient guidance for correct invocation.

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 0%, and the description offers no explanation for any of the 7 parameters (e.g., video_path, title, tags, privacy_status). The description only covers the tool's primary purpose but leaves parameter meaning entirely to the schema with no additional guidance.

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 uploads one vertical video as a YouTube Short. This verb-resource combination is distinct from sibling tools like youtube_list_recent_videos or youtube_oauth_authorize_url.

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 mentions dry-run default and live mode requirement, providing some context but no explicit when-not-to-use or comparison to alternatives. Siblings are different enough to not require detailed exclusion.

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