browser_console

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

With no annotations, the description carries full burden. It states logs are accumulated since session start and supports optional level filtering, but lacks details on side effects, size limits, or whether logs are cleared after reading.

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 short, front-loaded sentences efficiently convey the tool's purpose and key feature (optional level filter) without 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 read tool with one optional parameter and no required fields, the description covers the essential: it reads logs from session start with optional filter. Missing output format or persistence details, but adequate for the complexity.

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 single parameter 'level' is defined in schema with enum values; description adds that filtering is optional, which adds context. However, it does not explain the meaning of each level value.

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?

Description clearly states the tool reads accumulated console logs from browser's F12 Console, with optional level filtering and recording from session start. It is distinct from sibling tools like browser_screenshot or browser_eval.

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 implies the tool is for retrieving console logs, but provides no explicit guidance on when to use it versus alternatives (e.g., browser_eval for executing JS), nor any when-not scenarios.

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