chrome_console

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful scope context ('since the debugger attached' implies a bounded, non-persistent buffer), but says nothing about retention limits, when the buffer resets, or what clearing does.

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?

A single efficient sentence with the scoping constraint front-loaded and no filler. It is a sentence fragment without a verb, but that costs little.

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?

With no output schema, the description should characterize the returned message structure and the effect of 'clear'; it does neither. It never states the prerequisite that the debugger must already be attached for any messages to exist.

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 coverage is only 50%: tabId is documented in the schema (default: active tab) but 'clear' is bare in both schema and description. The description never mentions that clear discards captured messages, which is the one parameter most likely to surprise a caller.

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 names the resource precisely — console messages and exceptions from a tab — with the scoping qualifier 'since the debugger attached'. It is clear what this tool returns, though it never states an explicit verb (retrieve/list) and gives no differentiation from the near-identical sibling browser_console.

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?

There is no when-to-use guidance, no prerequisites (e.g., debugger must be attached), and no routing advice. The sibling list contains both browser_console and chrome_console, and the description does nothing to help an agent choose between them.

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