nex_browser_console_messages

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

With no annotations, the description carries the full behavioral burden. It reveals that messages are buffered (implying accumulation) but says nothing about whether reads consume/clear the buffer, what happens with the clear flag, whether this works after page navigation, or what the messages look like.

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. Efficient, though its brevity is achieved partly by omitting needed detail rather than by tight editing.

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 annotations and no output schema, the description must explain both semantics of the 'clear' flag and the shape of returned messages; it does neither. An agent can call it, but cannot predict the effect of clear or what it will receive.

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 67%: pageId and sessionId have defaults documented in the schema, but the 'clear' boolean is undocumented in both schema and description, leaving the potentially destructive buffer-clearing behavior ambiguous. The description adds nothing beyond the schema.

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 (read) and resource (console messages) plus a scope qualifier: messages buffered by this automation session. It is distinguishable from the sibling network diagnostic tools (nex_browser_network_requests, nex_browser_network_request) by resource type, though it doesn't explicitly contrast with them.

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?

No statement of when to call this versus nex_browser_network_requests or nex_browser_evaluate, and no prerequisites such as needing an active connection. The only guidance is implicit in the phrase 'buffered by this automation session'.

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