browser_console_messages

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

With no annotations, the description must disclose behavioral traits, but it only says 'Returns all console messages.' It fails to mention the default behavior (messages since last navigation), the level filtering hierarchy, or the optional file save behavior. The description is misleading by saying 'all' when the 'all' parameter defaults to false.

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, clear sentence with no fluff. It is front-loaded and efficient. However, it is so terse that it omits critical context, preventing a higher score for conciseness that balances completeness.

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 has four parameters, no output schema, and no annotations, yet the description provides almost no contextual information. It does not explain the 'all' parameter's effect, the level hierarchy, or the filename option. An agent would have to rely entirely on the schema, leaving significant gaps for a moderately complex tool.

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 detailed descriptions for all four parameters, resulting in 100% coverage. The tool description adds no additional parameter information, so it does not go beyond the schema. A baseline of 3 is appropriate because the schema carries the semantic load.

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 returns console messages, using a specific verb and resource. It distinguishes the general function from sibling tools like browser_network_requests, but it does not explicitly differentiate from alternatives or mention filtering capabilities, which would justify a 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 such as browser_network_requests or browser_evaluate. There is no mention of prerequisites, scenarios, or exclusions. The only implied context is browser console messages, which is insufficient.

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