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. While 'Read' implies a safe operation, it fails to specify what 'recent' means (time window vs. count), whether reading consumes/clears the error buffer, or the format of returned errors (stack traces, messages, etc.).

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 single sentence is appropriately front-loaded with the action verb and contains no redundant information. However, extreme brevity becomes a liability given the lack of supporting metadata in annotations or schema.

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 zero schema descriptions, no annotations, and no output schema, the description should explain behavioral details like error format, temporal scope of 'recent', and buffer behavior. As written, it's incomplete for a debugging tool requiring precise invocation 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?

Schema has 0% description coverage. The description only implicitly references 'session_id' via 'active session' but provides no guidance on the 'limit' parameter, its default value of 20, or valid range of 1-100. Insufficient compensation for the schema's lack of documentation.

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 provides a specific verb ('Read') and clear resource ('recent uncaught page errors'), distinguishing it from siblings like get_console or get_network_log. However, it doesn't explicitly clarify the difference between 'page errors' and 'console' output, which could confuse selection.

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?

No guidance provided on when to use this versus browser.get_console or browser.get_request_failures. No prerequisites mentioned beyond the implicit 'active session' requirement.

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