Get browser mode & state

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

No annotations provided, so description must carry full burden. It describes what is reported but omits behavioral traits like read-only nature, authentication requirements, or side effects. Agent cannot infer safety profile without explicit statements.

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?

Single sentence listing four output items is concise and front-loaded. Could be slightly improved with structured formatting (e.g., bullet list), but no 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?

Given no output schema, description adequately names returned data but lacks detail on types, possible values, or guarantees of field presence. Adequate for a simple info tool but not fully complete.

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?

Tool has zero parameters with 100% schema coverage (empty schema). Baseline 4 applies. Description adds value by explaining the output fields (mode, state, timeout, directory), compensating for lack of output schema.

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 specifies that the tool reports current browser configuration details (headless/headed, open state, idle timeout, profile directory). It distinguishes itself from sibling tools like set_browser_mode (mutation) and login_status (auth-related).

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 checking browser state before operations, but lacks explicit guidance on when to use this tool versus alternatives (e.g., login_status or set_browser_mode). No exclusions or prerequisites stated.

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