brave_summarizer

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

With minimal annotations (only title and openWorldHint), the description carries the full burden. It states the tool 'retrieves' summaries, indicating a read-only operation. It mentions optional features and prerequisites. However, it does not discuss error handling or rate limits, but overall behavior is clear.

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 well-structured with a clear opening sentence, bullet-pointed 'When to use' section, and a final paragraph covering requirements. Every sentence adds value; there is no fluff or repetition. It is appropriately sized for the tool's complexity.

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 three parameters and no output schema, the description covers purpose, prerequisites, optional features, and use cases adequately. It does not detail the output format beyond 'text summary', but that is sufficient for the tool's role as a summarizer.

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 fully described in the schema. The description adds context beyond the schema: it explains that 'key' comes from a prior search result, and describes the optional booleans as enabling inline references and entity info. This adds meaningful guidance.

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 retrieves AI-generated summaries via Brave's Summarizer API. It uses a specific verb ('retrieves') and resource ('summaries of web search results'), and distinguishes itself from sibling tools that perform other search types (image, local, news, video, web).

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 explicitly lists when to use (e.g., 'when you need a concise overview') and provides requirements: must first call brave_web_search with summary=true and requires a Pro AI subscription. It also implies when not to use by contrasting with sibling tools.

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