search_broll

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

Since no annotations are provided, the description carries the full burden. It transparently states 'Returns assets with direct, downloadable URLs (images: full_url, stock video: video_url).' This discloses the output format and indicates it's a read-only operation. No destructive behavior is implied.

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 compact at two sentences, front-loading the core purpose and then providing usage hints. Every sentence is informative without redundancy.

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 search tool with 3 parameters (one required) and no output schema, the description explains the return value (URLs) and hints at weighting. It is complete enough for an agent to use correctly. Minor gap: no mention of pagination or result limits, but not critical.

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 has 100% parameter description coverage (e.g., 'query' description, 'aspect' enum descriptions, 'weights' nested description). The description adds value by summarizing how to use weights and aspect, and by specifying the return URL types, which is not in the schema. This adds meaning beyond 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 the tool's purpose: 'Search B-Roll Studio for real, embeddable b-roll for a topic or moment.' It specifies the resource (B-Roll Studio) and the action (search), and differentiates from siblings which are about building scripts, timelines, downloading, or placing assets.

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 explicit usage guidance: 'Use the weights to bias the mix (0=off..3=heavy) and aspect to set the frame shape.' It does not explicitly state when not to use or mention alternatives, but the context is clear for an agent.

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