Browser Status

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

No annotations are provided, so the description carries the full burden, and it does disclose its read-only observational behavior ('Check...reports whether...lists all active session IDs') plus the connect-mode concept behind the debug port. It stops short of explicitly affirming no state is mutated or describing refresh/staleness of the report, but the signals are clear.

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?

Three short sentences, front-loaded with the core purpose, then the concrete outputs, then the usage context. No filler or redundant restatement of the title.

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?

An output schema exists, so return-value detail is not the description's responsibility. For a zero-parameter diagnostic tool, the description supplies purpose, outputs, and invocation timing, leaving nothing an agent needs before calling it.

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 takes zero parameters, so there is nothing for the description to disambiguate; the 'No parameters needed' note is confirmatory rather than additive. Baseline 4 applies for a parameterless tool.

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 (Check) and resource (browser readiness) and precisely enumerates what it reports: Chrome debug port availability for connect mode and all active Puppeteer session IDs. An agent can distinguish it from sibling inspection tools like browser_tabs or browser_profiles without opening schemas.

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?

Gives clear context: 'use this to verify the server is running and see which browser sessions are available before interacting with pages', establishing a pre-flight usage pattern. It does not, however, name any sibling alternative or state when not to use it, which matters in a 38-tool family.

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