Batch search

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

No annotations exist, so description must disclose behavior. It mentions parallelism, deduplication, caps on queries (6) and previews (12), and media type selection. However, it does not describe error handling, result format, or side effects, leaving gaps.

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 that are front-loaded with key functionality: parallelism, query limit, deduplication, and ideal use. 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?

No output schema, so description should outline what is returned; it does not. The parallelism and deduplication are well explained, but missing details on error handling, result structure, and relation to sibling tools. Adequate but not fully comprehensive.

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 only 17% (only previews has a description). The description adds meaning for queries (parallel, deduplicated) and previews (capped at 12), and mentions media type. But per_query, orientation, and preview_height are not elaborated, so compensation is partial.

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?

Description clearly states the tool runs up to 6 search queries in parallel with deduplication, and the use case for multi-scene content. Verb 'run' and resource 'search queries' are specific, distinguishing it from single-query siblings like search_photos and search_videos.

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?

Explicitly says 'Ideal for gathering candidates for a multi-scene piece of content', providing a clear context. Does not explicitly list when not to use or compare to alternatives, but the use case is well-defined.

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