console

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

Annotations only declare readOnlyHint/openWorldHint; the description adds genuinely new behavior: a 500-entry buffer created at tab creation, an exact return format string with timestamp and source location, and the fact that clear empties the buffer after reading. That last point is a side effect worth knowing and is not covered by annotations.

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?

Front-loaded with what the tool returns and then packed with the format and per-flag semantics; almost no waste. The clauses are dense and semicolon-chained, but each carries distinct information.

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?

No output schema exists, so the description supplies the return shape and cap itself; with zero required parameters and no nested objects, the only thing an agent needs to call it is covered here or in the schema. Nothing material is missing.

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 40%, and the description compensates by explaining three of the five parameters: level's enum semantics (notably that 'warning' includes warnings and errors), pattern as substring or /regex/, and clear's after-read behavior. Only limit and tab are left to the schema, which already documents both.

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?

States a specific verb-and-resource pair: console messages and uncaught page errors for a tab, with the buffer origin (tab creation) and cap (500) made explicit. It is clearly distinct from the sibling network tool, though it never names a sibling to differentiate against.

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 debugging use case is implied rather than stated, and there is no explicit guidance on when to reach for console instead of network, evaluate, or dialog. What guidance exists is per-parameter (what level and pattern mean), not situational.

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