BrowserCat MCP Server (Browser Automation)

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Execute JavaScript' implies a mutation operation (potentially changing page state), the description doesn't specify whether this is safe/reversible, what permissions are needed, how errors are handled, or what the execution context is (e.g., same-origin restrictions). It lacks critical behavioral details for a tool that can arbitrarily modify browser state.

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, clear sentence with zero wasted words. It's front-loaded with the core action ('Execute JavaScript') and specifies the context ('in the browser console'). Every word contributes directly to understanding the tool's 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?

Given the complexity of executing arbitrary JavaScript in a browser (a potentially dangerous operation with no annotations and no output schema), the description is insufficient. It doesn't cover safety considerations, error handling, execution context, or what happens to the script's return value. For a tool with such significant behavioral implications, more context is needed.

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 schema description coverage is 100% (the 'script' parameter is fully documented as 'JavaScript code to execute'), so the baseline is 3. The description doesn't add any parameter semantics beyond what the schema provides—it doesn't explain script format, return value handling, or execution constraints. However, with only one parameter that's well-documented in the schema, this is adequate.

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 'Execute JavaScript in the browser console' clearly states the action (execute) and target (JavaScript in browser console). It distinguishes this tool from its siblings (click, fill, hover, navigate, screenshot, select) by focusing on code execution rather than UI interaction. However, it doesn't specify what kind of JavaScript execution this is (e.g., evaluation, injection, or console command).

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 doesn't mention prerequisites (e.g., requires an active browser session), appropriate use cases (e.g., for dynamic content extraction vs. UI automation), or when other tools like browsercat_select might be more suitable. The agent must infer usage from the tool name and sibling context alone.

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