youtube_search

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

No annotations provided; description fails to mention authentication needs, rate limits, pagination behavior, or default sorting. Only states basic search action without behavioral nuances.

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?

One sentence is brief, but it omits critical contextual information. Could be improved by adding search type specifics and parameter guidance.

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 9 parameters, no output schema, and many YouTube-related siblings, the description is grossly incomplete. Does not explain parameter functions, return format, or search scope constraints.

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 only 33% (3 of 9 params have descriptions). Description adds no additional meaning for undocumented parameters like api_key, query, max_results, channel_id, region_code, or page_token.

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?

Clearly states verb ('Search'), resource ('YouTube'), and scope ('videos, channels, or playlists'). Differentiates from sibling tools like youtube_get_video or youtube_get_channel.

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?

No guidance on when to use this tool vs siblings (e.g., youtube_get_video, youtube_get_channel). Lacks any context about search scope or limitations.

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