browser_get_console_logs

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that unhandled promise rejections are captured (beyond plain console output), but says nothing about the bounded nature of "recent" (buffer size or retention), that the read is non-destructive unless `clear` is set, or what targeting happens when no tabId is supplied.

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 front-loaded sentence with no filler; the enumeration of captured categories is the most valuable information and appears immediately after the verb. Nothing would be gained by trimming it further.

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?

For a three-parameter read tool with no output schema and no annotations, the description covers what is captured but not what an entry looks like or how many are returned. An agent can call it correctly but cannot predict the response shape or the buffer limit.

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 100%, so `clear`, `tabId`, and `types` are already documented in the schema; the baseline of 3 applies. The description adds only the vague notion of "recent" and nothing about type filtering semantics or which tab is defaulted to.

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 ("Retrieves recent console logs") and enumerates the captured categories — warnings, runtime errors, unhandled promise rejections — which tells an agent exactly what data this surfaces. It never names the closest sibling (browser_get_network_logs), so differentiation relies on the tool name rather than the description.

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 mention of prerequisites such as being attached to a tab, and no routing to alternatives like browser_get_network_logs or browser_evaluate. Usage is only inferable from the word "console," which is the same level of guidance a bare name provides.

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