web_search

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

With no annotations provided, the description carries the full burden but only mentions the API used ('Brave Web Search API'). It lacks details on behavioral traits such as rate limits, authentication needs, error handling, or what the search results include, which are critical for a web search tool.

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 a single, efficient sentence with zero waste, clearly front-loaded with the core purpose. It's appropriately sized for a tool with multiple parameters, making it easy to parse quickly.

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 complexity of a web search tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error cases, or important constraints like the 'count' range (1-20), leaving significant gaps for the agent.

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 57% (4 out of 7 parameters have descriptions), so the baseline is 3. The description adds no additional parameter semantics beyond the schema, such as explaining enum values (e.g., 'freshness' options) or default behaviors, but doesn't compensate for the coverage gap.

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 verb ('Search') and resource ('the web'), specifying it uses the 'Brave Web Search API'. However, it doesn't differentiate from sibling tools like 'local_descriptions' or 'local_pois', which might also search but in different contexts, so it's not a perfect 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?

No guidance is provided on when to use this tool versus alternatives like 'local_descriptions' or 'rich_fetch'. The description only states what it does without context, prerequisites, or exclusions, leaving the agent to infer usage.

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