videos_searchVideos

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

With no annotations, the description must disclose behavioral traits. The single sentence 'Search for videos on YouTube' adds no behavioral context beyond the name. It does not mention pagination, rate limits, result ordering, or that it returns a list of videos. The schema implies behavior through parameters, but the description itself 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 very concise (one sentence), but it is too minimal for a tool with 13 parameters. While conciseness is valued, the description lacks substance needed to understand the tool's behavior. It earns its place but could be more informative without being verbose.

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 the complexity (13 parameters, no output schema), the description is incomplete. It does not explain what happens when no results are found, how pagination works, or what the response looks like. The schema documents parameters, but the description fails to provide operational context.

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?

Baseline is 3 because schema description coverage is 100%. The description does not add any additional meaning beyond what the schema provides for parameters. It simply restates the tool's function without elaborating on how parameters interact or their significance.

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 'Search for videos on YouTube' clearly states the verb and resource. However, it does not distinguish this tool from siblings like 'videos_getVideo' (which retrieves a single video) or 'channels_listVideos' (which lists videos for a specific channel). The purpose is clear but lacks specificity about the scope of the search.

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 is provided on when to use this tool versus alternatives. The description offers no context about typical use cases, prerequisites, or explicitly states when not to use it. This leaves the agent without insight into choosing between search and other video-related tools.

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