browser_console

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

With no annotations, the description bears full responsibility. It describes the clear parameter that mutates state by clearing the buffer, but omits details like whether logs persist across navigations or if buffer is cumulative. The basic reading operation is clear, but side effects and retention behavior are not fully disclosed.

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?

Extremely concise: one sentence for purpose and a bullet list for parameters. No redundancy, each word adds value. The structure is front-loaded with the main purpose.

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 states what is retrieved (console output and JS errors) and mentions the clear parameter. The output schema exists (though not shown), so return format documentation is partially offloaded. However, it does not specify whether output is an array, how errors are differentiated from logs, or what happens if no output exists. Slightly incomplete for a complete understanding.

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 0% description coverage, so the description's parameter explanations are essential. It adds "Target page ID" for page_id and "Clear the message buffer after reading" for clear, which clarifies the boolean's effect beyond the default value in the schema. For a simple two-parameter tool, this is adequate but not extensive.

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?

Clearly states the tool retrieves browser console logs and JS errors. Verb "Get" plus resource "browser console output" makes purpose unambiguous and distinct from siblings like browser_evaluate or browser_read_page.

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 on when to use this tool versus alternatives. For instance, it does not explain when to prefer this over browser_evaluate for retrieving logs or interacting with console. The description lacks contextual usage hints.

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