Auto-Browser

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

With no annotations provided, the description carries the full disclosure burden. It clarifies that profiles are 'reusable' and 'saved' (persistent), but omits read-only status, return format, pagination, or error conditions (e.g., empty list behavior).

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 efficient sentence with zero waste. It is front-loaded with the action verb 'List' and every modifier ('reusable', 'saved', 'loaded into a new session') adds necessary context about the resource type and its lifecycle.

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 tool, the description adequately explains the resource. However, with no output schema provided, it fails to hint at the return structure (e.g., whether it returns IDs, names, or full profile objects), leaving a gap in operational context.

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 input schema has zero parameters. Per the rubric, zero parameters warrants a baseline score of 4, as there are no semantics to clarify beyond what the empty schema already conveys.

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 uses a specific verb ('List') and clear resource ('reusable saved auth profiles'). It adds context that these are used for sessions ('loaded into a new session'), distinguishing it from listing tabs, sessions, or downloads. However, it does not explicitly contrast with sibling 'get_auth_profile'.

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 phrase 'loaded into a new session' implies usage context (retrieving profiles before creating/forking sessions), but there are no explicit when-to-use instructions, prerequisites, or named alternatives like 'save_auth_profile' or 'get_auth_profile'.

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