brave-search

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It omits key behaviors such as whether the search is read-only, API rate limits, authentication needs, result format, or side effects. The description adds no behavioral context beyond the basic function.

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 with no filler words, but it is under-specified. The 'Tools:' prefix suggests it might be a list entry, and the fragment-like structure does not provide enough detail to justify its brevity. It is not a complete standalone description.

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?

While an output schema exists, which reduces the need to explain return values, the description is still incomplete. The generic parameters, lack of annotations, and missing usage instructions mean the agent cannot confidently determine how to call the tool or what behavior to expect. The description fails to cover even basic invocation details.

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 input schema exposes two generic parameters, 'tool' and 'arguments,' both with null defaults and no descriptions (0% coverage). The description does not explain what these parameters mean or how to populate them, leaving the agent without the necessary information to invoke the tool correctly.

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 states 'Web search using Brave Search API,' which clearly conveys the tool's function of performing web searches via the Brave API. It distinguishes from sibling tools, none of which are search-related. However, the phrasing is a noun phrase with a 'Tools:' prefix, making it read like a list label rather than a proper imperative description, which slightly reduces clarity.

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 no indication of when to use this tool, no mention of alternatives, no prerequisites, and no exclusions. It is purely definitional, leaving an agent without any guidance on choosing this tool over others.

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