Browser Instrumentation MCP Server

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 states the tool destroys a session and cleans up resources, which implies mutation and resource release, but lacks details on permissions needed, whether destruction is reversible, error handling, or side effects. This is a significant gap for a destructive operation.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by structured Args and Returns sections. Every sentence earns its place without redundancy, making it efficient and well-organized.

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?

Given the tool's complexity (destructive operation), lack of annotations, and presence of an output schema (which covers return values), the description is partially complete. It explains the action and parameter but misses critical behavioral details like safety warnings or prerequisites, leaving gaps for an AI agent.

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 description adds meaning beyond the input schema by explaining that the 'name' parameter refers to 'Name of the session to destroy'. Since schema description coverage is 0% and there is only one parameter, this compensates well, though it could provide more context (e.g., format or examples).

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 specific action ('Destroy') and resource ('browser session'), distinguishing it from sibling tools like browser_session_create, browser_session_connect, and browser_session_list. It explicitly mentions cleaning up resources, which adds specificity beyond just the name.

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 implies usage context through the action 'destroy' and resource 'browser session', suggesting it should be used when ending a session. However, it does not explicitly state when to use it versus alternatives (e.g., browser_session_connect for reusing sessions) or provide exclusions, missing full explicit guidance.

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