brave_web_search_code_mode

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

With no annotations, the description adequately explains the sandbox execution, the DATA variable, and console.log output. It mentions 'secure QuickJS sandbox' but does not detail error behavior, rate limits, or authentication requirements.

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 very concise with two paragraphs: first explains functionality, second gives usage guidance and a code example. No superfluous content; every sentence adds value.

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 executing custom code, the description covers the core workflow and distinguishes from plain search. It lacks details on output format and error handling, but provides enough context for basic use.

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 coverage is 100%, so baseline is 3. The description adds value by providing a concrete JavaScript example for the 'code' parameter and explaining the 'DATA' variable, which goes beyond the schema's basic description.

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 it performs a web search and then executes custom JavaScript on the raw response, distinguishing it from plain search tools. It gives a specific use case ('broad information gathering... needing specific parts of the result') which differentiates it from siblings like brave_web_search.

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 explicitly states when to use (broad information gathering, recent events, needing specific parts) and implies when not to (for full results, use non-code version). However, it does not explicitly mention sibling names or provide contraindications.

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