Upload YouTube video

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

No annotations are provided, so the description carries the full behavioral burden. 'Defaults to private' is the only behavioral disclosure, and that merely restates the privacyStatus schema default. Nothing is said about the quota-heavy nature of YouTube uploads, permission requirements, file-size limits, or the result of the call.

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 short sentences, front-loaded with the core action and free of filler. The final sentence duplicates a schema default, which is a slight redundancy but not wasteful enough to drop below a 4.

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?

For a 9-parameter mutation tool with no annotations and no output schema, the description is thin. The schema covers inputs well, but the agent gets no insight into auth/account requirements, quota cost, or failure behavior for a potentially expensive 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 description coverage is 100%, so the schema already documents all 9 parameters. The description reiterates the path-vs-content preference and the private default, adding only marginal emphasis over what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('Upload a video to YouTube'), which is clearly distinct from siblings like google_youtube_update_video, google_youtube_get_video, or google_youtube_add_to_playlist. It just doesn't explicitly name those alternatives to help disambiguate.

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 gives parameter-choice guidance ('local file path (preferred) or base64 content'), which steers the agent toward the better input. However, it offers no guidance on when to use this tool versus alternatives, nor any prerequisites such as auth or account selection.

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