Auto-Browser

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

No annotations are provided, so the description carries the full burden. It mentions 'recent' but doesn't specify the time window or retention policy, doesn't define failure types (4xx, 5xx, timeouts), and doesn't disclose if reading clears the buffer or has other 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, efficiently structured sentence of seven words. Every word earns its place: 'recent' defines scope, 'failed' filters the data, 'network requests' defines the resource, and 'active session' defines the container 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?

For a two-parameter read operation without output schema or annotations, the description provides minimum viable context. However, gaps remain regarding output format, failure classification, and the definition of 'recent' given the lack of supporting structured metadata.

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?

With 0% schema description coverage, the description must compensate for both parameters. It implicitly references 'session_id' via 'active session' but provides no guidance on the 'limit' parameter's behavior, default value, or maximum constraints beyond what's in the 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 uses a specific verb ('Read') and resource ('failed network requests') with clear scope ('recent', 'active session'). It implicitly distinguishes from sibling 'get_network_log' by specifying 'failed' and from 'get_page_errors' by specifying 'network requests'.

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?

While the phrase 'for an active session' implies a prerequisite, the description lacks explicit guidance on when to use this versus 'get_network_log' (all traffic) or 'get_page_errors' (JavaScript errors), and doesn't clarify what constitutes a 'failed' request.

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