youtube_search

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

With no annotations, the description carries the full burden. It discloses that the tool uses YouTube's InnerTube API and returns normalized results, and explains pagination behavior. However, it does not address rate limits, authentication, or non-destructiveness, which are important for behavioral transparency.

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 concise with four sentences, front-loading the purpose. Each sentence provides necessary information without redundancy or irrelevant detail.

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 purpose, API source, pagination, and parameter aliases, but lacks details about the return format (no output schema provided) and does not explain the effect of other filter parameters. For a search tool with 9 parameters and no output schema, more context would be beneficial.

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 100%, so baseline is 3. The description adds value by clarifying that q is the primary parameter and search_query is an alias, and by explaining how to use continuation_token for pagination. This goes beyond the schema's individual parameter descriptions.

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 action 'Search YouTube' and the resource, with additional details about returning normalized results and using the InnerTube API. It distinguishes this tool from sibling YouTube tools like youtube_channel_search by being a general search.

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 mentions pagination via continuation_token and the alias relationship between q and search_query, but does not provide explicit guidance on when to use this tool versus other YouTube search tools (e.g., youtube_channel_search, youtube_playlist). Usage is implied but not differentiated.

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