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 for behavioral disclosure. It states the tool inspects data but doesn't clarify if this is read-only (likely, but not confirmed), whether it requires specific page states or permissions, what format the output takes, or any limitations (e.g., cross-origin restrictions). The reference to 'browser_docs' suggests additional context exists elsewhere, but the description itself lacks essential behavioral details for safe and effective use.

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 very concise—a single sentence that directly states the tool's purpose. It's front-loaded with the core action ('inspect') and resource. However, the parenthetical reference to 'browser_docs' feels tacked on and doesn't integrate smoothly, slightly reducing clarity. Overall, it's efficient with minimal waste.

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 (inspecting structured browser storage), lack of annotations, and no output schema, the description is incomplete. It doesn't address key contextual aspects like output format, error conditions, dependencies on page state, or how it differs from other storage tools. The reference to external docs hints at missing information, but the description itself fails to provide a self-contained understanding for the 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?

Schema description coverage is 100%, with both parameters clearly documented in the schema. The description adds no parameter-specific information beyond what the schema provides—it doesn't explain the relationship between databaseName and objectStoreName, valid naming conventions, or example values. Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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's purpose as 'Inspect IndexedDB databases and their data' with a specific verb ('inspect') and resource ('IndexedDB databases and their data'). It distinguishes from most siblings by focusing on storage inspection rather than navigation, interaction, or performance monitoring. However, it doesn't explicitly differentiate from other storage-related tools like 'browser_storage_get_cache_storage' or 'browser_storage_get_service_workers' beyond the database type.

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 minimal guidance, only referencing 'browser_docs' for more information without stating when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., when IndexedDB inspection is needed over other storage methods), or exclusions. This leaves the agent with little direction on appropriate usage scenarios.

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