search_youtube_videos

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

With no annotations, the description carries the full burden, but it only says 'Search...' and discloses no behavior such as auth requirements, result count limits, or read-only nature. It doesn't contradict the absent annotations, but it adds no behavioral context beyond the action.

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 with no filler or repeated schema details. Every word earns its place.

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 two-parameter search tool with an output schema, the description is minimally viable: it names the resource and the one required input. However, it omits usage context and behavioral details that the lack of annotations otherwise leaves open.

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 0%, and the description only reinforces what 'query' is; it adds no meaning for max_results, such as whether it caps the number of returned videos or has an upper bound. The parameter names are self-explanatory, but the low-coverage schema required more compensation.

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 is a clear imperative: 'Search YouTube videos by query' specifies the action (search), resource (YouTube videos), and input (query). It is adequately distinct from siblings like get_trending_videos and search_bilibili_videos, though it doesn't explicitly contrast them.

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 when-to-use guidance is provided. The agent is not told to prefer this over search_bilibili_videos, get_video_details, or get_trending_videos, and there are no exclusions or prerequisites mentioned.

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