Browser MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states what the tool does but doesn't disclose whether this is destructive, requires specific permissions, has side effects, or what happens after unregistration. The reference to 'browser_docs' hints at more information but doesn't provide it directly.

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 extremely concise (one sentence with a reference). It's front-loaded with the core action. However, the reference to 'browser_docs' feels like a placeholder rather than earned content, slightly reducing efficiency.

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 that performs a potentially destructive operation (unregistering service workers) with no annotations and no output schema, the description is inadequate. It doesn't explain what unregistering entails, what the expected outcome is, or any error conditions. The reference to external docs doesn't compensate for missing core context.

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?

Schema description coverage is 100%, with the single parameter 'scopeURL' clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for high schema coverage without adding value.

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 states the tool's purpose ('Unregister a service worker'), which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like 'browser_storage_get_service_workers' or 'browser_storage_delete_cache', and the reference to 'browser_docs' is vague rather than specific.

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. The description only references 'browser_docs' without explaining what that contains or how it relates to usage decisions. There's no mention of prerequisites, timing, or comparison to sibling storage tools.

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