youtube_search

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no further behavioral context such as pagination behavior, result shape, or how multiple scopes interact, so it contributes little beyond the annotations.

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 filler. It efficiently communicates the core purpose and the main modes of operation, earning its place without redundancy.

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?

For a tool with seven parameters, multiple scope modes, nested schema structures, and no output schema, the one-line description is too sparse. It omits details about pagination, locale handling, the meaning of 'within' in transcript/channel scopes, and what a search result contains, leaving the agent under-informed for complex calls.

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 0%, so the description must compensate for seven undocumented parameters. It only hints at scope-related parameters ('within a channel or transcript', 'get trending videos') and says nothing about query, limit, cursor, locale, or filters. This is insufficient parameter guidance.

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 states a specific action ('Search') on a clear resource (YouTube) and enumerates the distinct modes: global, within a channel, within a transcript, or trending videos. This clearly distinguishes it from sibling tools that fetch a single video, channel, or playlist.

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 searching rather than retrieving known entities, and the scope enum adds mode context, but it does not explicitly say when to prefer this tool over youtube_video_get, youtube_channel_get, or youtube_playlist_get. No exclusions or alternative-selection guidance are provided.

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