brave_search

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

The description adds context beyond the readOnlyHint annotation by mentioning 'No approval needed' and the return format (top results with title, URL, description). This provides useful behavioral details about the tool's safety profile and expected output, without contradicting the annotation.

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 concise and front-loaded, stating the purpose in the first phrase. Every sentence adds value: the API source, the return fields, and the approval/read-only status. No unnecessary words.

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?

For a simple 2-parameter tool with an output schema present, the description is complete. It clarifies the tool's purpose, output shape, and approval requirements. There is no missing critical context that would hinder an agent from using the tool correctly.

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?

The schema has no parameter descriptions (0% coverage), so the description must compensate. The description implies that 'query' is the search string and 'count' limits the number of top results, but it does not explicitly define these parameters. The parameter names are self-explanatory enough for basic use, but the description could add more explicit semantics.

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: 'Search the web using the Brave Search API.' It specifies the resource (web via Brave), the action (search), and the return format (top results with title, URL, and description). This distinguishes it from the unrelated sibling tools, which focus on server management and execution.

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 provides clear context for when to use the tool: whenever a web search is needed. It also states 'No approval needed — read-only,' which serves as a guideline for invoking it without approval workflows. While it does not explicitly name alternatives or exclusions, the sibling tools are unrelated, so the context is sufficient.

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