brave_videos

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

With no annotations, the description carries full burden. It discloses that results are fetched from public Brave Search video HTML and may return 503 on challenges, providing valuable error context. It also mentions default locale settings, offering reasonable transparency for a search tool.

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: first clearly states purpose, second adds defaults and error behavior. Every sentence adds value with no redundancy. Front-loaded and efficient.

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 8 parameters with full schema, no output schema, and no annotation, the description covers purpose, source, errors, and defaults. It lacks output structure details but is fairly complete for a search tool. Agent can infer return type from name.

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%, so parameters are well-documented. The description adds default values and context about data source/errors but does not enhance individual parameter meaning beyond the schema. Per guidelines, baseline 3 applies.

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 Brave video results and returns normalized results for a query string. The verb 'search' and resource 'Brave video results' are specific, and it distinguishes itself from siblings like brave_search, brave_images, and brave_news by focusing on 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?

The description does not explicitly provide guidance on when to use this tool versus alternatives (e.g., google_videos, bing_videos). It implies use for video search from Brave but lacks exclusions or comparisons, leaving the agent to infer context.

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