Enhanced Web Scraper MCP Server

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 it mentions analysis of 'component tree, props, and state', it doesn't describe what the tool actually does behaviorally: Does it launch a browser? Does it require React DevTools? Is it read-only or does it modify the app? What's the output format? The description is too vague about the tool's operational behavior.

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, efficient sentence that gets straight to the point: 'Inspect React Native web app with component tree, props, and state analysis.' There's no wasted verbiage, and it's appropriately sized for the tool's complexity. Every word earns its place.

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 (6 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain what the tool actually produces as output, how it interacts with the app, or what behavioral constraints exist. For an inspection tool that presumably launches browsers and analyzes React applications, more context about the operation and results 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?

Schema description coverage is 100%, so the schema already documents all 6 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. It mentions 'component tree, props, and state analysis' which loosely maps to 'includeComponentTree' and 'includeState' parameters, but doesn't provide additional semantic context. Baseline 3 is appropriate when schema does the heavy lifting.

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: 'Inspect React Native web app with component tree, props, and state analysis.' It specifies the verb ('inspect'), resource ('React Native web app'), and scope of analysis. However, it doesn't explicitly differentiate from sibling tools like 'test_react_app' or 'inspect_element', which could have overlapping functionality.

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. With siblings like 'test_react_app', 'inspect_element', and 'check_expo_dev_server', there's no indication of when this inspection-focused tool is preferred over testing or other inspection tools. The description lacks any 'when-to-use' or 'when-not-to-use' context.

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