browser-console

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only mentions 'streaming support', which is a useful detail, but it omits any side effects (e.g., opening a browser, executing scripts, potential resource usage), prerequisites, or what happens to the browser session. It also does not describe the return format or how streaming terminates.

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, front-loaded sentence that states the core action and a key feature. It contains no filler or redundant information, making it appropriately concise and well-structured.

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 tool's complexity (5 parameters, no output schema, no annotations), the description is too minimal. It does not explain the waitFor or commands parameters, which represent significant behaviors, nor does it clarify what the captured console output looks like. The schema covers parameters but the description fails to provide a complete mental model of the tool's capabilities.

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 100%, so all parameters (url, stream, timeout, waitFor, commands) have descriptive schema definitions. The tool description adds nothing beyond the schema—'streaming support' repeats the stream parameter's purpose. Therefore, baseline 3 is appropriate.

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 tool navigates to a URL and captures console output from the browser, with streaming support. This specific verb+resource combination ('navigate' + 'capture console output') and the qualifier 'from the browser' distinguishes it from the sibling tool 'browser-server-console', which likely targets a server-side console.

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 usage for capturing browser console output after navigation, but it does not explicitly state when to use this tool versus alternatives, mention exclusions, or provide use-case context (e.g., debugging front-end errors). The presence of a sibling tool suggests a potential distinction but it is not articulated.

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