browser_status

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

No annotations are provided, so the description carries the burden. It discloses the exact target (Brave process and CDP endpoint 127.0.0.1:9222), which is useful behavioral context, but it omits return format, timeout/error behavior, and whether the check has any side effects.

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?

A single, front-loaded sentence where every clause adds needed specificity (browser, condition, address). There is no filler or repetition.

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?

The tool is simple and the description covers the diagnostic purpose, but with no annotations and no output schema it does not say what the status result looks like (e.g., boolean/status object) or what happens if the check fails. For an agent to interpret the call, that is a real gap.

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 tool takes zero input parameters, so the baseline is 4. The description adds no parameter meaning because none exist, and nothing is missing in that dimension.

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?

States a specific verb (Check) and two precise conditions (whether Brave is running and whether CDP is reachable on a specific address). This clearly distinguishes it from the action-oriented sibling tools such as browser_navigate or browser_click.

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?

Usage is implied by the diagnostic nature — an agent would call it to verify the browser connection before using other browser_* tools — but the description does not explicitly state when to use it, when not to use it, or name alternatives such as browser_prepare.

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