brave_search

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

Given no annotations, the description carries full burden. It describes returned results comprehensively (web results, pagination, related queries, etc.) and mentions pagination offset. Missing info on auth, rate limits, or read-only nature, but the detail provided is substantial.

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?

Three concise sentences: purpose, time filtering guidance, locale defaults. No unnecessary words, but could be slightly more structured (e.g., separate sections for return types and parameters).

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 compensates by listing return types (web results, pagination, etc.). Parameter coverage is good with usage tips. However, it lacks any mention of error handling, rate limits, or authentication, which would be beneficial given no annotations.

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 has 100% coverage, but description adds value beyond schema by explaining how time_range and date_from/date_to work together, and explicitly mentioning locale defaults. This helps users understand parameter relationships and defaults.

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 'Search Brave' and lists returned items (web results, pagination, related queries, discussions, videos, knowledge card). However, it does not explicitly differentiate from other search siblings like google_search or bing_search, which have similar features.

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?

Provides guidance on time filters (time_range vs date_from/date_to) and defaults for locale, but no advice on when to choose Brave Search over alternatives such as google_search or bing_search.

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