search_videos

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state that this is a read-only operation, describe result shape or pagination, or mention any rate limits. It also loosely says 'videos' while the schema's type parameter permits channels and playlists, making the actual scope slightly misleading.

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 names the main action and the key filter dimensions without wasted words. It is appropriately sized for a search tool.

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 schema is rich enough to carry parameter meaning, and the tool's expected search-result behavior is fairly intuitive. However, with no output schema and no annotations, a bit more context about result format, default behavior, or when not to use this tool would make it fully complete.

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 100% of parameters, each with meaningful descriptions and enums, so the description need not repeat parameter details. The phrase 'upload date, duration, sort order, and content type' adds mild orientation but no semantics 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 clearly states the tool searches YouTube with a specific set of filters. It names the resource and the capabilities, but it does not distinguish itself from siblings like search_transcript or search_within_channel, and it says 'videos' while the schema allows channel and playlist types.

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?

There is no guidance on when to use this tool versus alternatives such as search_transcript, search_within_channel, or get_trending_videos. The description implies general YouTube search, but it does not state exclusions, prerequisites, or the conditions that would make a sibling tool more appropriate.

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