youtube_search

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

No annotations are present, so the description must carry the full burden. It only states the action and result type but omits critical behavioral traits such as whether results are paginated, required authentication, or the potential for side effects. The default behavior (e.g., always returns videos unless type is set) is not explained.

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 that efficiently communicates the core purpose. It is not verbose and contains no extraneous information, though it could be slightly more precise given the tool's actual capabilities.

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?

The tool has 3 parameters and no output schema. The description does not explain what the returned 'ranked video results' contain (e.g., IDs, titles, thumbnails) or how ranking works. Given the absence of annotations or output schema, the description is insufficient for an agent to fully understand the tool's behavior and output.

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 covers all three parameters (query, type, limit) with descriptions, defaults, and constraints, so schema_description_coverage is 100%. The description adds no extra meaning beyond what the schema provides, meeting the baseline expectation.

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 verb 'Search' and resource 'YouTube', and mentions 'ranked video results', making the core purpose apparent. However, it is slightly misleading because the type parameter allows searching channels and playlists, not just videos. It distinguishes well from sibling tools (get_transcript, save_summary) which have different functions.

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 explicit when-to-use or when-not-to-use guidance relative to siblings. It gives only a general statement of searching YouTube, leaving usage context implied. No alternatives or exclusions are mentioned.

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