youtube_search_niche

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

No annotations are provided, so the description must carry behavioral disclosure. It states the output type (video IDs, basic metadata) and sort behavior, and explicitly disclaims metric calculations. However, it omits limitations like quota usage, pagination, or authentication requirements, which are relevant in YouTube API tools. The added context about 'raw results' is useful but incomplete.

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?

Two sentences, cleanly front-loaded with the action and result, followed by usage guidance. No redundant wording or filler. Every sentence contributes value.

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 5 parameters and no output schema, so the description should specify return value structure more explicitly. 'Basic metadata' is vague—does it include title, channel, publish date? Also no mention of quota or pagination. The presence of youtube_quota_status as a sibling suggests quota is a concern, which should be noted. Overall, it's minimally complete but leaves 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?

The input schema already covers all parameters with descriptions (100% coverage), so the description adds little beyond referencing the sort order. It doesn't clarify parameter details further, but the schema is sufficient. Baseline 3 is appropriate.

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 for videos in a niche or category and returns video IDs plus basic metadata sorted by order. This differentiates it from siblings like youtube_get_video_details, youtube_analyse_niche, and youtube_get_thumbnails by focusing on raw search results without metric analysis.

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?

It provides explicit usage context: 'Use this for targeted searches when you already have video IDs from a previous search or want raw search results without metric calculations.' This signals when to prefer this tool over analysis-heavy siblings, though it doesn't name an alternative directly. The phrase about having video IDs is slightly confusing but the overall guidance is helpful.

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