searchVideos

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

The description adds useful behavioral context beyond the annotations, such as that the tool returns 'videoId or channelId needed for other tools' and mentions filtering capabilities. The annotations already declare readOnlyHint and idempotentHint, so the description complements them well.

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 three sentences, front-loaded with purpose, and every sentence adds essential information. No fluff or repetition.

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 (8 parameters, no output schema) and rich schema coverage, the description covers the main use cases and return values. It could mention pagination or default behavior for omitted parameters, but the schema handles most details.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by specifying that type defaults to 'video' and emphasizing the MUST condition for channel search. It also highlights the key return values (videoId/channelId) which are not in the schema.

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 it's a universal search tool for YouTube content, with the ability to find videos (default) or channels. This distinguishes it from sibling tools like getChannelStatistics or getVideoDetails, which are more specific.

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 provides clear context for when to use the tool (e.g., 'Use this to find videos or channels') and gives explicit guidance on parameter usage ('To find a specific content creator, you MUST set type to channel'). It does not explicitly mention alternatives among siblings but the context is sufficient.

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