search_media

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool uses yt-dlp search, which suggests a read-only operation, but does not explicitly confirm it is non-destructive or mention any side effects, permission requirements, or rate limits. Adequate but could be more explicit.

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 concise sentences that immediately convey the tool's purpose, scope, and supplementary nature. No redundant words; every sentence adds 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 description explains the tool's purpose and method, but lacks details about output structure or how results relate to sibling tools (extract_info, get_transcript). Without an output schema, the description should guide the agent on what to expect from results. Adequate but not 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?

Schema coverage is 100% with each parameter fully described. The tool description adds context about yt-dlp and platform mapping (e.g., 'youtube → ytsearch:'), but the schema already covers the enum values. Thus, the description adds marginal value beyond the schema, meeting the baseline.

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 explicitly states the verb 'Search' and resource 'media', specifies supported platforms (YouTube, etc.) and the underlying technology (yt-dlp), and clarifies its role as a supplementary discovery tool, which clearly distinguishes it from siblings like extract_info and get_transcript.

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 mentions it is a 'supplementary discovery tool meant to complement web search', implying when to use it for media discovery, but does not explicitly state when not to use it or name alternatives. It provides implied context but lacks clear exclusions.

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