youtube_search

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

No annotations are provided, so the description carries the burden of disclosure. It does state the result attributes (channel, duration, view count, publish date), giving some behavioral context. However, it does not explicitly state that this is a read-only operation or mention any rate limits, pagination, or result ordering, leaving some gaps.

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 two sentences long, with the first stating the action and outcome and the second giving when-to-use guidance. Every word earns its place; there is no redundancy or fluff.

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?

With 4 parameters and no output schema, the description provides a reasonable overview of what the tool returns (channel, duration, view count, publish date) and when to use it. Minor details like result ordering and pagination are not mentioned, but the schema covers limits and the core purpose is clear.

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 coverage is 100%, with each parameter already well described in the input schema. The description does not add extra parameter-level detail; it only paraphrases the query purpose and result fields. Therefore, the baseline of 3 is appropriate.

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 the tool's function: 'Search YouTube for videos with channel, duration, view count and publish date.' It specifies the resource (YouTube) and the scope (videos) with key result attributes, distinguishing it from sibling search tools like google_search or google_news.

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 gives explicit usage context: 'Use this when the user wants video content, tutorials or talks.' It does not mention when not to use or name alternative tools, but the context is clear enough to guide selection among the listed siblings.

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