upload_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. It does reveal parameter-driven behaviors — publish_at is required when visibility='scheduled', and made_for_kids is a COPPA compliance flag — but omits upload quota limits, file format/size constraints, and processing latency, which materially affect calling an upload tool.

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?

Front-loaded one-line purpose followed by a structured Args block; appropriate length for a 9-parameter tool. The pseudo-code Args style is slightly heavier than prose but every line carries parameter meaning.

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?

An output schema exists, so return values need not be explained. The description adequately covers the 9 params for correct invocation, with the only real gaps being the missing usage guidance and behavioral caveats noted above.

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% (only titles), so the description must compensate, and it does: all 9 params are documented with meaning, defaults (category_id='22', visibility='private'), the 100-char title limit, valid visibility values, and the conditional requirement on publish_at. A few entries are thin ('description: Video description text'), keeping it below 5.

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?

States a specific verb+resource: 'Upload a video file to the authenticated YouTube channel.' This is unambiguous and distinct from 'update_video_metadata', 'set_video_visibility', and the other siblings, which all operate on already-uploaded videos.

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 when-to-use guidance is given. With siblings like update_video_metadata and set_video_visibility, the agent gets no explicit rule for choosing upload_video over them, and no stated prerequisites despite YouTube requiring OAuth auth.

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