brave_summarizerRetrieves AI-generated summaries of web search results. Two-step flow: first call brave_web_search with summary=true to obtain summarizer.key, then pass it here. Pro AI tier required.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Summarizer key returned by a prior `brave_web_search` with `summary=true`. | |
| entity_info | No | Whether to include extra entity-info fields with citation metadata. |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / entity_info / defaultRemoved value: -falseInput schema / properties / entity_info / descriptionPrevious value: -"Returns extra entities info with the summary response."New value: +"Whether to include extra entity-info fields with citation metadata."Input schema / properties / inline_referencesRemoved value: -{
- "default": false,
- "description": "Adds inline references to the summary response.",
- "type": "boolean"
-}Input schema / properties / key / descriptionPrevious value: -"The key is equal to value of field key as part of the Summarizer response model."New value: +"Summarizer key returned by a prior `brave_web_search` with `summary=true`."Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true and destructiveHint=false; description adds operational context (two-step flow, tier requirement) without contradicting annotations.
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 sentences, front-loaded with purpose, each sentence adds value with no fluff.
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 exists; description lacks details about the summary output format. However, parameters are fully covered and operational flow is clear.
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 baseline is 3. Description mentions 'key' in context but adds no new semantic meaning beyond what the schema provides for either parameter.
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?
Description clearly states 'Retrieves AI-generated summaries of web search results' and distinguishes from sibling tools by explaining the two-step flow involving brave_web_search.
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?
Explicitly describes the two-step flow and prerequisite ('first call brave_web_search with summary=true'), and states 'Pro AI tier required', providing clear usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.