Search YouTube Videos

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It adds that only public videos are searched and that only one explicit page is returned, which is useful. But it does not mention auth requirements, rate limits, or the read-only nature beyond the verb 'searches'.

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 sentence that immediately communicates the core function. It is front-loaded and contains no filler words.

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?

Given that there is no output schema, the description should describe the return fields of 'normalized metadata', but it does not. It also lacks details on pagination behavior and parameter semantics, making the tool under-documented.

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 input schema has 0% description coverage and the description does not elaborate on 'query', 'limit', 'order', or 'pageToken'. The schema's enum and defaults provide some meaning, but the description fails to explain how pagination or ordering works, leaving significant gaps.

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 uses the specific verb 'searches' and identifies the resource as 'public YouTube videos', clearly distinguishing it from sibling tools that retrieve or list videos by ID or channel. The phrase 'one explicit page' further sharpens the scope.

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 implies the tool is for keyword-based search of public videos, which differentiates it from sibling tools like youtube_get_video or youtube_get_channel_videos. However, it does not explicitly state when not to use alternatives.

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