Search YouTube videos

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it returns titles, IDs, and channels, but omits important details such as whether the search uses the default account, how results are limited, or any authentication requirements. This lack of disclosure is a significant gap for a tool that relies on user account context.

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 a single, front-loaded sentence that directly states the tool's purpose and output. There is no wasted wording, making it highly concise and easy to scan.

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?

The description covers the core function and return fields, and the schema handles parameter details. However, it lacks context about the account parameter (e.g., whether it uses the default account) and does not explicitly mention that results are limited by maxResults, leaving some ambiguity for a multi-account environment.

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?

All parameters (query, account, maxResults) have descriptions in the input schema, and the description adds no additional parameter semantics. With 100% schema coverage, the baseline is 3; the description does not go beyond this, but it does not need to.

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 specifies the action ('Search YouTube for videos') and the return values ('titles, IDs and channels'). This distinguishes it from sibling tools like google_youtube_get_video (which retrieves a specific video) and google_youtube_my_videos (which lists the user's own 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?

The description provides clear context that this tool is for searching YouTube videos. However, it does not explicitly mention when not to use it or compare it to alternatives, though the purpose is unambiguous enough for most use cases.

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