browser_get_console

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

With no annotations provided, the description must fully disclose behavior. It only states 'get' with no mention of return format, whether messages are cleared, session requirements, or read-only guarantees. While 'get' implies a non-destructive read, the description does not explicitly convey any behavioral traits.

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 a single, direct sentence with no filler or redundancy. It is front-loaded and immediately clear, making it optimally concise for the information it contains.

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?

There is no output schema and no annotations, so the description should explain return values and usage context. It only states 'Get console messages from the browser' without describing what the console messages include, whether sessionId is required, or how to handle multiple sessions. This incomplete context leaves an agent under-informed for correct invocation.

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?

The schema provides full description coverage for the single parameter sessionId, described as 'Browser session ID'. The description adds no additional meaning about how sessionId is used or the effect of omitting it, so it relies entirely on the schema, which is already sufficient.

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 uses a specific verb 'get' and clearly identifies the resource as 'console messages', which is distinct from sibling getters such as browser_get_text or browser_get_network. It unambiguously states the tool's function, though it adds no additional scope or filter details.

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 offers no guidance on when to use this tool versus alternatives. It does not mention debugging scenarios, prerequisites such as an active session, or exclusions like whether it works without a session ID. No contextual usage direction is provided.

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