search_videos

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

No annotations are provided, so the description must carry full behavioral burden. It only states the basic action and does not disclose what the response contains, whether it returns a list, any sorting/filtering limitations, or other behavioral traits. For a tool with no annotation coverage, this is insufficient.

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 concise sentence with no redundant phrasing. Every word earns its place, and it is immediately clear what the tool does.

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 simple read-only search tool with complete parameter schema, the description is minimally adequate. However, without an output schema, it does not explain what kind of results are returned (e.g., metadata fields, video IDs), and it lacks any context about limitations or the difference from sibling retrieval tools. It meets the baseline but has clear gaps.

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% for both parameters (query and maxResults), so the baseline is 3. The description's mention of 'keyword' merely restates the query parameter and adds no additional semantic meaning beyond what the schema already provides.

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 uses a specific verb ('Search') and resource ('YouTube videos') with a clear method ('by keyword'). It clearly distinguishes from sibling tools which all retrieve specific entities (transcript, video info, channel info) rather than performing discovery.

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 use for finding videos by keyword, and sibling names suggest it is the discovery tool. However, it does not explicitly state when to use this tool over alternatives or mention any exclusions (e.g., 'use get_video_info for details on a specific video').

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