inspect_browser_console

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely restates the tool's purpose without explaining side effects, return values, how errors are collected, or whether it modifies the browser session. This is insufficient for an agent to anticipate the tool's behavior.

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, concise sentence that is front-loaded and easy to parse. It could be slightly more expansive, but it does not waste words and effectively communicates the core action.

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?

The tool lacks annotations, an output schema, and parameter descriptions, making the description the only source of context. The minimal sentence fails to clarify critical aspects such as what taskId refers to, how pathname influences inspection, or what format the console errors are returned in. Given the tool's likely complexity, this is a significant gap.

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 has no descriptions for 'taskId' or 'pathname', and the description does not mention them at all. With 0% schema coverage, the description should compensate but does not, leaving agents to guess what these parameters mean and how they affect the inspection.

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 clearly states the tool's function with a specific verb ('inspect') and resource ('browser console errors'). However, it does not distinguish from the sibling tool 'get_console_errors', which likely performs a similar function, so it earns a 4 rather than 5.

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 guidance is provided on when to use this tool versus alternatives like 'get_console_errors' or 'inspect_network_failures'. There is no context about prerequisites, exclusions, or preferred sequencing, so this dimension is poorly addressed.

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