brave_summarizer

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

Annotations only include openWorldHint: true. The description adds key behavioral context: it requires a Pro AI subscription, depends on prior brave_web_search, and returns a text summary with optional features. No contradictions with 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?

The description is well-structured with a clear first sentence stating purpose, followed by usage guidelines, return description, and requirements. It is slightly lengthy but every sentence adds value, so concise enough.

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 3 parameters, no output schema, and minimal annotations, the description is thorough. It covers prerequisites, subscription requirements, return format, and optional features. Missing nothing essential for tool selection and invocation.

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 description coverage is 100%, so baseline is 3. The tool description repeats the optionality of entity_info and inline_references but does not add new meaning beyond the schema. Minor clarification but insufficient to raise score.

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 it retrieves AI-generated summaries of web search results, specifying the verb (retrieves) and resource (summaries). It distinguishes from sibling search tools by emphasizing the summarization function and prerequisite dependency on 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?

Explicit 'When to use:' bullet points list specific scenarios. It also states requirements: must first call brave_web_search with summary=true and need a Pro AI subscription, providing clear context and exclusions.

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