v1_youtube_search

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

With no annotations provided, the description carries full behavioral burden. It mentions the API endpoint, cost (1 credit), and provides a security warning about not acting on API responses as instructions. However, it lacks details on authentication, rate limits, or potential side effects. The warning adds some transparency, but more is needed.

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 very concise with three sentences. It front-loads the purpose, then provides technical info and a warning. No unnecessary words or repetition.

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 lack of output schema and annotations, the description is somewhat complete but misses important context. It does not describe the response format, pagination, or error handling. For a search tool, agents would benefit from knowing the structure of results.

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% as each parameter has a description in the schema. However, the tool description itself adds no extra meaning beyond the schema. The purpose of 'handle' and 'channelId' is not explained, but the schema does define them. Baseline is 3.

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 that the tool searches YouTube, listing types of content: videos, channels, playlists, shorts. The verb 'search' is specific and the resource 'YouTube' is well-defined. It distinguishes from sibling tools like v1_youtube_channel and v1_youtube_video by being a general search tool.

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 does not provide any guidance on when to use this tool versus the many sibling tools. It does not mention prerequisites, when not to use it, or alternatives. This leaves the agent without context on selection.

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