YouTube Search API

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

No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. The description only mentions 'search results' and 'metadata' but does not clarify pagination, rate limits, result ordering, or any constraints. This minimal transparency leaves significant gaps for an agent relying on this description.

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 with no redundant information. It is succinct but could arguably include a few more useful details (e.g., pagination) without becoming overly verbose, settling just above the minimum viable standard.

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 the absence of an output schema and annotations, the description is insufficiently complete. It does not outline what a response may contain beyond 'video titles and metadata,' nor does it mention pagination tokens (sp) or other behavioral aspects. The description feels underspecified for a tool with 4 parameters and no structured output metadata.

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 schema description coverage is 100%, with each parameter already explained (search_query, sp, country, language). The description adds no additional parameter-specific details beyond the schema, so the baseline score 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: 'Retrieve YouTube search results with video titles and metadata.' It uses a specific verb (retrieve) and a specific resource (YouTube search results), which distinguishes it from sibling tools like youtube_video or youtube_transcripts that target specific content types.

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?

There is no guidance on when to use this tool versus alternatives like google_search or youtube_transcripts. The description only states what the tool does, leaving it to the agent to infer appropriate use cases without explicit context or exclusions.

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