Auto-Browser

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it fails to state that this is a read-only operation, what data structure is returned (tab IDs, titles, URLs, or full objects), or whether there are rate limits or 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?

The description is a single, efficient sentence with the action front-loaded. It avoids redundancy, though the term 'pages' is somewhat redundant with 'tabs' in a browser context.

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?

With no output schema and 0% input schema coverage, the description is incomplete. It omits crucial information about the return value (what attributes of tabs are returned) and insufficiently documents the required session_id parameter given the lack of schema support.

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?

Given 0% schema description coverage, the description partially compensates by referencing 'one session', which maps to the session_id parameter. However, it does not describe the parameter's format, that it is required, or where to obtain it (e.g., from create_session or list_sessions).

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 states a specific verb ('List') and resource ('currently open tabs/pages') and scopes it to 'one session', which distinguishes it from sibling tools like list_sessions or list_auth_profiles. However, it does not clarify how this differs from get_session, which may also return tab information.

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 provides no explicit guidance on when to use this tool versus alternatives (e.g., get_session), nor does it state prerequisites such as needing to first create or obtain a valid session_id via create_session or list_sessions.

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