Browser Read Console

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

With no annotations, the description carries the full burden. It discloses that reading is non-destructive unless drain=true, which clears the buffer, a useful behavioral trait. However, it does not describe return format, pagination, whether it blocks, or potential side effects beyond drain. For a read operation, this is adequate but not rich; it lacks context like what happens if the buffer is empty or whether errors are aggregated.

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 two sentences with zero waste. The primary purpose is front-loaded in the first sentence, and the drain behavior is added as a separate line. Every word earns its place, making it highly efficient and scannable.

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 4 parameters, an output schema, and no annotation coverage, the description is incomplete. It lacks details on n, tab, and session semantics, and does not clarify the nature of the output (e.g., whether it returns structured logs, timestamps, or just text). While the output schema may cover return structure, the parameter gaps and lack of behavioral context leave the agent guessing on how to invoke it correctly.

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 description coverage is 0%, so the description must compensate for all parameters. It only explains drain (to clear the buffer), leaving n (likely number of messages), tab (which tab), and session (which session) completely unexplained. The agent has no idea what n controls (count? index?), how tab selection works, or session context. This is a significant gap for a 4-parameter tool.

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 verb 'Read' and the resource 'console messages and page errors', listing specific types (JS errors, logs, failed asserts). It distinguishes the tool's core function from sibling tools like browser_network_get (network) or browser_read_dialogs (dialogs) through its focus on console, though it doesn't explicitly name any alternative. This is clear but not overtly differentiated.

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 gives a concrete usage tip: 'Set drain=true to clear the buffer after reading.' This implies when to use the drain parameter but does not provide guidance on when to use this tool versus alternatives, nor any conditions or prerequisites. The hint about drain is helpful but leaves the broader usage context implicit.

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