Get console messages

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

The description explains that output is captured 'since the last navigation' and that the 'all' parameter can include earlier messages, offering useful behavioral context. Annotations confirm read-only and non-destructive nature with no contradictions.

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 extremely concise, using two short sentences to convey both purpose and usage hints, with no wasted 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?

The description is sufficient for an agent to understand what the tool does and how to apply basic filters, though it lacks explicit mention of the return format or structure. Given the simplicity, this is adequate.

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 schema provides descriptions for all three parameters, and the tool description adds practical context about filtering. While the schema covers 100% of parameters, the description's filter guidance enhances understanding beyond the basic 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 states the tool's purpose with a specific verb ('Return') and resource ('console output'), making it distinct from sibling tools like browser_network_requests or browser_snapshot.

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 usage guidance by mentioning filtering options ('Filter by level or regex') to control output, but does not explicitly name alternative tools or when to prefer this one over others.

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