brave_summarizer

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

Discloses optional features (inline_references, entity_info) and requirements (Pro AI subscription, prior web search). The openWorldHint annotation hints at external impact, but the description does not elaborate on side effects; however, the tool is likely read-only for summarization.

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?

Well-organized with bullet points and clear sections. Slightly verbose in the 'When to use' list, but overall efficient and front-loaded with purpose.

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?

Covers prerequisites, optional features, and return type (text summary). Lacks details on output format or example, but the tool is simple enough that the description is sufficient.

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%, and the description adds context beyond the schema: explains that 'key' comes from a previous search result and that entity_info and inline_references are optional enhancements. This helps an agent understand parameter usage in workflow.

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?

Clearly states it retrieves AI-generated summaries from web search results using Brave's Summarizer API. Distinguishes from sibling tools like brave_web_search and brave_llm_context by specifying it processes search results into concise summaries.

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 explicit 'When to use:' bullet points covering overviews, fact-checking, user summaries, and research. Also mentions prerequisites (prior web search with summary=true, Pro AI subscription) but does not explicitly state when not to use or compare to alternatives.

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