youtube_upload_video

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

With no annotations, the description carries the full burden. It discloses cost (1,600 quota units), default privacy status ('private by default'), and the scheduling constraint (publish_at requires private). It omits the return value (e.g., video ID) but covers important behavioral traits for a mutation 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?

The description is well-structured with a clear opening sentence followed by cost and default behavior, then a bullet-style list of arguments. Every sentence earns its place without redundancy, making it both concise and scannable.

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 tool with 7 parameters and no output schema, the description covers all parameter semantics and key behavioral context. It doesn't mention the return value or error cases, but these are not critical for an upload tool. Overall it feels complete enough for an agent to invoke correctly.

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?

The description adds substantial meaning beyond the input schema. It explains each parameter's constraints: absolute path, max title length, max description length, category default, privacy options, and the condition for publish_at. This is high-value semantic enrichment for all 7 parameters.

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 'Upload a video to YouTube' with a specific verb and resource. It distinguishes from sibling tools like youtube_update_video and youtube_delete_video by focusing on the upload action.

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 provides clear context for use (uploading a video) and mentions cost (1,600 quota units) and default privacy behavior. It doesn't explicitly state when not to use it, but the sibling tools make the distinction obvious. No exclusions are needed for a simple upload operation.

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