search_web

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

With no annotations, the description must fully disclose behavior. It usefully states the default keyless mode, the 20-result cap, Brave API key requirement, and operator support variability. However, it does not disclose output format, pagination, rate limits, or error behavior, leaving notable gaps.

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 concise sentences front-load the core purpose and then provide essential constraints and provider options. There is no filler or redundant restating of schema fields.

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?

The tool is simple and the description covers the essential call parameters: query, limit, provider, and max results. However, with no output schema and no annotations, the description should say more about what the returned results look like and any operational constraints (e.g., rate limits or engine coverage) for an agent to fully rely on it.

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 0% description coverage, so the description carries the parameter burden. It explains provider semantics and key requirements, and 'Max 20 results' adds meaning to the limit parameter. Query is left to inference and the limit parameter's exact role is not explicitly mapped, so compensation is only partial.

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 uses a specific verb and resource ('Find public mentions') and clearly identifies the default behavior as keyless metasearch. It does not explicitly distinguish from sibling search tools like search_username or search_archives, so it falls short of a 5.

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 gives provider-level guidance ('Omit provider to use the configured default') and notes Brave's key requirement, but it provides no guidance on when to choose this tool over sibling tools such as search_archives or search_shodan. There is no explicit when-to-use or when-not-to-use guidance for the tool itself.

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