status

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states a 'check' action, which implies a read-only operation, but it does not disclose what specific state information is returned, whether any side effects occur, or whether connection status includes network latency, WebSocket, etc. This is minimal transparency.

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 sentence that is direct and free of unnecessary words. Given the tool's simplicity (no parameters), this conciseness is appropriate and every word contributes to conveying the purpose.

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 tool with no parameters and no output schema, the description is adequate but lacks completeness. It does not explain what 'browser state' entails or what the response will contain (e.g., a status code, JSON fields). The simplicity of the tool might make this acceptable, but the description could still provide more detail about the returned information.

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 tool has zero parameters, and the schema coverage is 100% (trivially). Since there are no parameters to describe, the baseline score of 4 applies, and the description correctly focuses on the tool's action without parameter-related ambiguity.

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 'Check current connection status and browser state' uses a clear verb ('check') and identifies the resource (connection status and browser state). It clearly describes the tool's purpose but does not explicitly differentiate from sibling tools like browser_snapshot or browser_console_messages that also inspect browser state.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or cases where another sibling (e.g., browser_performance_metrics) would be more appropriate. The usage context is only implied by the purpose.

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