brave_web_search

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

The description discloses the return format ('relevant web pages with titles, URLs, and descriptions'), which is helpful. However, with no annotations provided, the description carries the burden for behavioral disclosure, and it does not mention rate limits, error behavior, or other non-obvious traits. It partially fulfills the requirement.

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 two concise sentences that front-load the verb and resource. There is zero wasted text, and every word earns its place.

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 the tool's complexity (7 parameters, no output schema, no annotations), the description is sufficient. The schema handles parameter details, and the description covers purpose and return format. It could mention rate limits or pagination, but those are not critical for a simple search tool.

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 the baseline is 3. The main description adds no parameter-specific meaning beyond what the schema already provides, but it does not need to since all parameters are well-documented.

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's function with a specific verb and resource: 'Search the web using Brave Search API.' It also specifies the output format ('Returns relevant web pages with titles, URLs, and descriptions'), leaving no ambiguity about the tool's purpose.

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?

There is no explicit guidance on when to use this tool or alternatives, but with no sibling tools, the context is clear. The description implies usage for web search but does not provide explicit when-to-use or when-not-to-use instructions.

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