browser_status

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

With no annotations, the description must bear the full burden. 'Get' implies a read-only operation, but it does not explicitly state that it does not modify the browser state, nor describe potential error conditions (e.g., if no browser session exists) or what 'connection info' specifically includes. It adds some context about contents but leaves behavioral details vague.

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 efficiently communicates the tool's purpose and scope without redundancy. Every word contributes meaning.

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 zero-parameter, zero-output-schema tool, the description provides a reasonable indication of what the tool returns ('opened tabs and connection info'). However, it omits details about the return format or whether it reports on the current page only or all pages, which could be relevant given the sibling toolset. Still, it is adequate for a simple status snapshot.

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 accepts zero parameters, so per the rubric the baseline is 4. The description does not need to explain parameter semantics since there are none, and the schema is fully covered by having no properties.

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's function with a specific verb ('Get') and resource ('browser and page status'), and it enumerates key contents (opened tabs, connection info). It distinguishes itself from sibling tools like browser_listTabs by focusing on overall status rather than just tabs, though it does not explicitly name an alternative.

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?

There is no guidance on when to use this tool versus the many sibling tools. It does not mention alternative tools like browser_listTabs or browser_title, nor any prerequisites or contexts where this status snapshot is preferable. The description simply states what it does.

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