Console Messages

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

Annotations only supply the safe-read profile, but the description discloses the real behavioral traps: capture begins only when a CDP tool first touches the tab, there is no history to read back, and pre-capture messages are unrecoverable. It also documents the caller's prerequisite (DevTools engine) and the ordering of results ('Newest last'), which the annotations cannot convey.

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?

Five tight sentences, front-loaded with purpose and result content before the capture and ordering caveats. Every sentence carries distinct information (what is captured, ordering, prerequisite, capture window, call-order advice) with no filler.

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 must characterize the returned data, and it does: entry kinds plus 'Newest last'. What remains thin is the shape of an individual entry (fields such as timestamp, source, stack) and behavior under the clear flag, though the schema covers the latter.

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?

With 100% schema description coverage the schema already explains all four parameters, including the tab_id fallback rule and the clear/level/limit semantics. The description adds the ordering context ('Newest last') that helps interpret limit, but nothing beyond that; baseline 3 applies.

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?

Specific verb+resource ('Read the console output of a tab') with an explicit enumeration of what counts as console output: console.log and friends, uncaught exceptions, and browser messages such as blocked requests and CSP violations. This clearly separates it from the sibling network_requests/network_entries tools.

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?

Gives a concrete when-to-use rule ('Call this tool ... before the action you want to observe') and names the alternative enabling path (cdp_status then any CDP tool). It does not state exclusions versus siblings (e.g. when to prefer network_requests for network data), so it falls just short of a 5.

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