browser_console_log

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

With no annotations, the description carries the full burden of disclosing behavior. 'Monitor console.log/warn/error' is extremely vague: it doesn't clarify whether monitoring persists across page navigations, whether it accumulates logs in memory, what happens on stop, or how the 'get' action returns data. The tool's statefulness and side effects (if any) are completely undisclosed.

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 concise and free of filler, fitting within one short sentence. It effectively communicates the high-level purpose without excess. However, the brevity borders on under-specification, as it omits critical details about the action parameter and behavior, so it doesn't earn a 5.

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 the tool has a single enum parameter and no output schema, the description still fails to explain observable behavior: what 'start' and 'stop' do, how 'get' returns logs, or what happens to accumulated logs. The existence of a sibling tool for getting logs adds confusion without clarity. The description is insufficient for an agent to use the tool correctly across all three actions.

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 has 100% parameter description coverage, but the only description is 'Action'—essentially meaningless. The enum values (start, stop, get) are listed, but their semantics are not explained. The tool description doesn't elaborate on these actions either, so the parameter meaning remains ambiguous. Baseline 3 applies due to high coverage, but the description adds no value beyond the schema's minimal text.

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 'Monitor console.log/warn/error' clearly identifies the resource (console logs) and a specific action (monitor), which differentiates it from the sibling tool 'browser_get_console_logs' that likely retrieves logs. However, it doesn't explicitly state that this tool manages a monitoring session via start/stop/get actions, which would fully distinguish it from simply fetching logs.

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 is provided on when to use this tool versus alternatives like browser_get_console_logs. The actions start/stop/get suggest a lifecycle, but their intended usage contexts and prerequisites are not explained. There is no mention of when monitoring is useful or when to use 'get' instead of directly retrieving logs.

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